text:
// Package
///////////////
package com.hp.hpl.jena.vocabulary;

// Imports
///////////////
import com.hp.hpl.jena.rdf.model.*;

/**
 *

 * Defines a vocabulary of RDF constants used by the latest release of DAML+oil
 * for class and property names.  The contract maintained by the DAML_OIL class
 * is that it will be periodically updated to reflect the latest release of DAML+OIL.
 * Currently this is the March 2001 release.  Older versions of the DAML+OIL
 * vocabulary, for compatability with older ontology documents, are maintained in
 * classes named DAML_OIL_YYYY_MM, for example DAML_OIL_2000_12.
 *

 *

 * Note that rudimentary support for multiple versions of DAML namespaces is
 * included in this release, by the mechanism of providing methods with the same
 * names as the static constants in the {@link DAMLVocabulary} interface.  This mechanism
 * is still under design review, and may change in future versions of Jena.
 *

 *

 * Note also that the capitalisation of
 * the constants herein is designed to follow normal practice in the RDF community, rather
 * than normal practice in the Java community. This is consistent with the capitalisation
 * of constants in Jena.
 *

 *
 * @author Ian Dickinson, HP Labs (email)
 * @version CVS info: $Id: DAML_OIL.java,v 1.2 2009-10-06 13:04:43 ian_dickinson Exp $
 */
public class DAML_OIL
    implements DAMLVocabulary
{
    // Constants
    //////////////////////////////////

    /** Singleton instance reference */
    private static DAML_OIL s_instance = new DAML_OIL();

    /** Model to hold the vocab resoures */
    private static Model s_model = ModelFactory.createDefaultModel();

    /* Resources */

    /** DAML namespace resource for the current release */
    public static final Resource NAMESPACE_DAML = s_model.createResource( NAMESPACE_DAML_2001_03_URI );

    /** DAML namespace resource for daml:collection. Note: strictly
     * daml:collection is only a string, not a resource in the DAML namespace. */
    public static final Resource collection = s_model.createResource( NAMESPACE_DAML_2001_03_URI+"collection" );

    /** RDF resource for DAML List class.   */
    public static final Resource List = s_model.createResource( NAMESPACE_DAML_2001_03_URI + "List" );

    /** RDF resource for DAML UniqueProperty class */
    public static final Resource UniqueProperty = s_model.createResource( NAMESPACE_DAML_2001_03_URI + "UniqueProperty" );

    /** RDF resource for DAML TransitiveProperty class */
    public static final Resource TransitiveProperty = s_model.createResource( NAMESPACE_DAML_2001_03_URI + "TransitiveProperty" );

    /** RDF resource for DAML UnambiguousProperty class */
    public static final Resource UnambiguousProperty = s_model.createResource( NAMESPACE_DAML_2001_03_URI + "UnambiguousProperty" );

    /** RDF resource for DAML Restriction class */
    public static final Resource Restriction = s_model.createResource( NAMESPACE_DAML_2001_03_URI + "Restriction" );

    /** RDF resource for DAML Ontology class */
    public static final Resource Ontology = s_model.createResource( NAMESPACE_DAML_2001_03_URI + "Ontology" );

    /** RDF resource for the nil (empty) list.  */
    public static final Resource nil = s_model.createResource( NAMESPACE_DAML_2001_03_URI + "nil" );

    /** RDF resource for the top type (i.e. the super-type of all types).  */
    public static final Resource Thing = s_model.createResource( NAMESPACE_DAML_2001_03_URI + "Thing" );

    /** RDF resource for the bottom type (i.e. the super-type of no types).  */
    public static final Resource Nothing = s_model.createResource( NAMESPACE_DAML_2001_03_URI + "Nothing" );

    /** Alias for rdfs:Literal in the daml namespace.  */
    public static final Resource Literal = s_model.createResource( NAMESPACE_DAML_2001_03_URI + "Literal" );

    /** RDF resource for DAML Class class (a DAML sub-class of rdfs:Class).   */
    public static final Resource Class = s_model.createResource( NAMESPACE_DAML_2001_03_URI + "Class" );

    /** RDF resource for DAML Datatype class (a DAML sub-class of rdfs:Class).   */
    public static final Resource Datatype = s_model.createResource( NAMESPACE_DAML_2001_03_URI + "Datatype" );

    /** RDF resource for DAML DatatypeProperty class (a DAML sub-class of rdf:Property).   */
    public static final Resource DatatypeProperty = s_model.createResource( NAMESPACE_DAML_2001_03_URI + "DatatypeProperty" );

    /** RDF resource for DAML ObjectProperty class (a DAML sub-class of rdf:Property).   */
    public static final Resource ObjectProperty = s_model.createResource( NAMESPACE_DAML_2001_03_URI + "ObjectProperty" );

    /** Alias for rdfs:Property in the daml namespace.  From 2001/03 onwards, use of ObjectProperty or DatatypeProperty is suggested. */
    public static final Resource Property = s_model.createResource( NAMESPACE_DAML_2001_03_URI + "Property" );

    /* Properties */

    /** RDF Property for the DAML versionInfo property */
    public static Property versionInfo = null;

    /** RDF Property for the DAML imports property on Ontologies */
    public static Property imports = null;

    /** RDF Property for the DAML disjointWith property on Classes */
    public static Property disjointWith = null;

    /** RDF Property for the DAML disjointUnionOf property on Classes */
    public static Property disjointUnionOf = null;

    /** RDF Property for the DAML sameClassAs property on Classes */
    public static Property sameClassAs = null;

    /** RDF Property for the DAML samePropertyAs property on Properties */
    public static Property samePropertyAs = null;

    /** RDF Property for the oneOf property on DAML class expressions */
    public static Property oneOf = null;

    /** RDF Property for the intersectionOf property on class expressions */
    public static Property intersectionOf = null;

    /** RDF Property for the unionOf property on class expressions  */
    public static Property unionOf = null;

    /** RDF Property for the complementOf property on class expressions */
    public static Property complementOf = null;

    /** RDF Property for the equivalentTo property on DAML values */
    public static Property equivalentTo = null;

    /** RDF Property for the DAML onProperty property on Restrictions */
    public static Property onProperty = null;

    /** RDF Property for the DAML toClass property on Restrictions */
    public static Property toClass = null;

    /** RDF Property for the DAML hasValue property on Restrictions */
    public static Property hasValue = null;

    /** RDF Property for the DAML hasClass property on Restrictions */
    public static Property hasClass = null;

    /** RDF Property for the DAML hasClassQ property on Restrictions */
    public static Property hasClassQ = null;

    /** RDF Property for the DAML cardinality property on Restrictions */
    public static Property cardinality = null;

    /** RDF Property for the DAML minCardinality property on Restrictions */
    public static Property minCardinality = null;

    /** RDF Property for the DAML maxCardinality property on Restrictions */
    public static Property maxCardinality = null;

    /** RDF Property for the DAML cardinalityQ property on Restrictions */
    public static Property cardinalityQ = null;

    /** RDF Property for the DAML minCardinalityQ property on Restrictions */
    public static Property minCardinalityQ = null;

    /** RDF Property for the DAML maxCardinalityQ property on Restrictions */
    public static Property maxCardinalityQ = null;

    /** RDF Property for the DAML inverseOf property on Properties */
    public static Property inverseOf = null;

    /** RDF Property for the DAML first property on Lists */
    public static Property first = null;

    /** RDF Property for the DAML rest property on Lists */
    public static Property rest = null;

    /** RDF Property for the DAML item property on Lists */
    public static Property item = null;

    /** Alias for rdfs:subPropertyOf in daml namespace */
    public static Property subPropertyOf = null;

    /** Alias for rdf:type in daml namespace */
    public static Property type = null;

    /** Alias for rdf:value in daml namespace */
    public static Property value = null;

    /** Alias for rdfs:subClassOf in daml namespace */
    public static Property subClassOf = null;

    /** Alias for rdfs:domain in daml namespace */
    public static Property domain = null;

    /** Alias for rdfs:range in daml namespace */
    public static Property range = null;

    /** Alias for rdfs:label in daml namespace */
    public static Property label = null;

    /** Alias for rdfs:comment in daml namespace */
    public static Property comment = null;

    /** Alias for rdfs:seeAlso in daml namespace */
    public static Property seeAlso = null;

    /** Alias for rdfs:isDefinedBy in daml namespace */
    public static Property isDefinedBy = null;

    /** RDF Property for the DAML sameIndividualAs property on instances */
    public static Property sameIndividualAs = null;

    /** RDF Property for the DAML differentIndvidualFrom property on instances */
    public static Property differentIndividualFrom = null;

    // Static variables
    //////////////////////////////////

    static {
            // properties:
            versionInfo       = s_model.createProperty( NAMESPACE_DAML_2001_03_URI, "versionInfo" );
            imports           = s_model.createProperty( NAMESPACE_DAML_2001_03_URI, "imports" );
            disjointWith      = s_model.createProperty( NAMESPACE_DAML_2001_03_URI, "disjointWith" );
            disjointUnionOf   = s_model.createProperty( NAMESPACE_DAML_2001_03_URI, "disjointUnionOf" );
            sameClassAs       = s_model.createProperty( NAMESPACE_DAML_2001_03_URI, "sameClassAs" );
            samePropertyAs    = s_model.createProperty( NAMESPACE_DAML_2001_03_URI, "samePropertyAs" );
            equivalentTo      = s_model.createProperty( NAMESPACE_DAML_2001_03_URI, "equivalentTo" );
            oneOf             = s_model.createProperty( NAMESPACE_DAML_2001_03_URI, "oneOf" );
            intersectionOf    = s_model.createProperty( NAMESPACE_DAML_2001_03_URI, "intersectionOf" );
            unionOf           = s_model.createProperty( NAMESPACE_DAML_2001_03_URI, "unionOf" );
            complementOf      = s_model.createProperty( NAMESPACE_DAML_2001_03_URI, "complementOf" );
            onProperty        = s_model.createProperty( NAMESPACE_DAML_2001_03_URI, "onProperty" );
            toClass           = s_model.createProperty( NAMESPACE_DAML_2001_03_URI, "toClass" );
            hasValue          = s_model.createProperty( NAMESPACE_DAML_2001_03_URI, "hasValue" );
            hasClass          = s_model.createProperty( NAMESPACE_DAML_2001_03_URI, "hasClass" );
            hasClassQ         = s_model.createProperty( NAMESPACE_DAML_2001_03_URI, "hasClassQ" );
            cardinality       = s_model.createProperty( NAMESPACE_DAML_2001_03_URI, "cardinality" );
            cardinalityQ      = s_model.createProperty( NAMESPACE_DAML_2001_03_URI, "cardinalityQ" );
            minCardinality    = s_model.createProperty( NAMESPACE_DAML_2001_03_URI, "minCardinality" );
            minCardinalityQ   = s_model.createProperty( NAMESPACE_DAML_2001_03_URI, "minCardinalityQ" );
            maxCardinality    = s_model.createProperty( NAMESPACE_DAML_2001_03_URI, "maxCardinality" );
            maxCardinalityQ   = s_model.createProperty( NAMESPACE_DAML_2001_03_URI, "maxCardinalityQ" );
            inverseOf         = s_model.createProperty( NAMESPACE_DAML_2001_03_URI, "inverseOf" );
            first             = s_model.createProperty( NAMESPACE_DAML_2001_03_URI, "first" );
            rest              = s_model.createProperty( NAMESPACE_DAML_2001_03_URI, "rest" );
            item              = s_model.createProperty( NAMESPACE_DAML_2001_03_URI, "item" );
            subPropertyOf     = s_model.createProperty( NAMESPACE_DAML_2001_03_URI, "subPropertyOf" );
            type              = s_model.createProperty( NAMESPACE_DAML_2001_03_URI, "type" );
            value             = s_model.createProperty( NAMESPACE_DAML_2001_03_URI, "value" );
            subClassOf        = s_model.createProperty( NAMESPACE_DAML_2001_03_URI, "subClassOf" );
            domain            = s_model.createProperty( NAMESPACE_DAML_2001_03_URI, "domain" );
            range             = s_model.createProperty( NAMESPACE_DAML_2001_03_URI, "range" );
            label             = s_model.createProperty( NAMESPACE_DAML_2001_03_URI, "label" );
            comment           = s_model.createProperty( NAMESPACE_DAML_2001_03_URI, "comment" );
            seeAlso           = s_model.createProperty( NAMESPACE_DAML_2001_03_URI, "seeAlso" );
            isDefinedBy       = s_model.createProperty( NAMESPACE_DAML_2001_03_URI, "isDefinedBy" );

            sameIndividualAs        = s_model.createProperty( NAMESPACE_DAML_2001_03_URI, "sameIndividualAs" );
            differentIndividualFrom = s_model.createProperty( NAMESPACE_DAML_2001_03_URI, "differentIndividualFrom" );
    }

    // Instance variables
    //////////////////////////////////

    // Constructors
    //////////////////////////////////

    /**
     * Constructor is private to ensure that only a single instance is available.
     */
    private DAML_OIL() {
    }

    // External signature methods
    //////////////////////////////////

    /**
     * Answer the namespace URI for a the current vocabulary. Note that this value is used to
     * construct the constants in the vocabulary, assuring that they are in the correct namespace
     * for this release.
     *
     * @return the namespace URI as a string.
     */
    public String getNamespace() {
        return NAMESPACE_DAML_2001_03_URI;
    }

    /**
     * Answer the singleton instance of this vocabulary
     *
     * @return The singleton instance
     */
    public static DAMLVocabulary getInstance() {
        return s_instance;
    }

    // The following methods provide the implementations for the DAMLVocabulary interface

    /** Answer the DAML namespace resource for the current release */
    @Override
    public Resource NAMESPACE_DAML() { return NAMESPACE_DAML; }

    /** Answer the RDF resource for DAML List class.   */
    @Override
    public Resource List() { return List; }

    /** Answer the RDF resource for DAML UniqueProperty class */
    @Override
    public Resource UniqueProperty() { return UniqueProperty; }

    /** Answer the RDF resource for DAML TransitiveProperty class */
    @Override
    public Resource TransitiveProperty() { return TransitiveProperty; }

    /** Answer the RDF resource for DAML UnambiguousProperty class */
    @Override
    public Resource UnambiguousProperty() { return UnambiguousProperty; }

    /** Answer the RDF resource for DAML Restriction class */
    @Override
    public Resource Restriction() { return Restriction; }

    /** Answer the RDF resource for DAML Ontology class */
    @Override
    public Resource Ontology() { return Ontology; }

    /** Answer the RDF resource for the nil (empty) list.  */
    @Override
    public Resource nil() { return nil; }

    /** Answer the RDF resource for the top type (i.e. the super-type of all types).  */
    @Override
    public Resource Thing() { return Thing; }

    /** Answer the RDF resource for the bottom type (i.e. the super-type of no types).  */
    @Override
    public Resource Nothing() { return Nothing; }

    /** Answer the Alias for rdfs:Literal in the daml namespace.  */
    @Override
    public Resource Literal() { return Literal; }

    /** Answer the RDF resource for DAML Class class (a DAML sub-class of rdfs:Class).   */
    @Override
    public Resource Class() { return Class; }

    /** Answer the RDF resource for DAML Datatype class (a DAML sub-class of rdfs:Class).   */
    @Override
    public Resource Datatype() { return Datatype; }

    /** Answer the RDF resource for DAML DatatypeProperty class (a DAML sub-class of rdf:Property).   */
    @Override
    public Resource DatatypeProperty() { return DatatypeProperty; }

    /** Answer the RDF resource for DAML ObjectProperty class (a DAML sub-class of rdf:Property).   */
    @Override
    public Resource ObjectProperty() { return ObjectProperty; }

    /* Properties */

    /** Answer the RDF Property for the DAML versionInfo property */
    @Override
    public Property versionInfo() { return versionInfo; }

    /** Answer the RDF Property for the DAML imports property on Ontologies */
    @Override
    public Property imports() { return imports; }

    /** Answer the RDF Property for the DAML disjointWith property on Classes */
    @Override
    public Property disjointWith() { return disjointWith; }

    /** Answer the RDF Property for the DAML disjointUnionOf property on Classes */
    @Override
    public Property disjointUnionOf() { return disjointUnionOf; }

    /** Answer the RDF Property for the DAML sameClassAs property on Classes */
    @Override
    public Property sameClassAs() { return sameClassAs; }

    /** Answer the RDF Property for the DAML samePropertyAs property on Properties */
    @Override
    public Property samePropertyAs() { return samePropertyAs; }

    /** Answer the RDF Property for the oneOf property on DAML class expressions */
    @Override
    public Property oneOf() { return oneOf; }

    /** Answer the RDF Property for the intersectionOf property on class expressions */
    @Override
    public Property intersectionOf() { return intersectionOf; }

    /** Answer the RDF Property for the unionOf property on class expressions  */
    @Override
    public Property unionOf() { return unionOf; }

    /** Answer the RDF Property for the complementOf property on class expressions */
    @Override
    public Property complementOf() { return complementOf; }

    /** Answer the RDF Property for the equivalentTo property on DAML values */
    @Override
    public Property equivalentTo() { return equivalentTo; }

    /** Answer the RDF Property for the DAML onProperty property on Restrictions */
    @Override
    public Property onProperty() { return onProperty; }

    /** Answer the RDF Property for the DAML toClass property on Restrictions */
    @Override
    public Property toClass() { return toClass; }

    /** Answer the RDF Property for the DAML hasValue property on Restrictions */
    @Override
    public Property hasValue() { return hasValue; }

    /** Answer the RDF Property for the DAML hasClass property on Restrictions */
    @Override
    public Property hasClass() { return hasClass; }

    /** Answer the RDF Property for the DAML hasClassQ property on Restrictions */
    @Override
    public Property hasClassQ() { return hasClassQ; }

    /** Answer the RDF Property for the DAML cardinality property on Restrictions */
    @Override
    public Property cardinality() { return cardinality; }

    /** Answer the RDF Property for the DAML minCardinality property on Restrictions */
    @Override
    public Property minCardinality() { return minCardinality; }

    /** Answer the RDF Property for the DAML maxCardinality property on Restrictions */
    @Override
    public Property maxCardinality() { return maxCardinality; }

    /** Answer the RDF Property for the DAML cardinalityQ property on Restrictions */
    @Override
    public Property cardinalityQ() { return cardinalityQ; }

    /** Answer the RDF Property for the DAML minCardinalityQ property on Restrictions */
    @Override
    public Property minCardinalityQ() { return minCardinalityQ; }

    /** Answer the RDF Property for the DAML maxCardinalityQ property on Restrictions */
    @Override
    public Property maxCardinalityQ() { return maxCardinalityQ; }

    /** Answer the RDF Property for the DAML inverseOf property on Properties */
    @Override
    public Property inverseOf() { return inverseOf; }

    /** Answer the RDF Property for the DAML first property on Lists */
    @Override
    public Property first() { return first; }

    /** Answer the RDF Property for the DAML rest property on Lists */
    @Override
    public Property rest() { return rest; }

    /** Answer the RDF Property for the DAML item property on Lists */
    @Override
    public Property item() { return item; }

    /** Answer the alias for rdfs:subPropertyOf in daml namespace */
    @Override
    public Property subPropertyOf() { return subPropertyOf; }

    /** Answer the alias for rdf:type in daml namespace */
    @Override
    public Property type() { return type; }

    /** Answer the alias for rdf:value in daml namespace */
    @Override
    public Property value() { return value; }

    /** Answer the alias for rdfs:subClassOf in daml namespace */
    @Override
    public Property subClassOf() { return subClassOf; }

    /** Answer the alias for rdfs:domain in daml namespace */
    @Override
    public Property domain() { return domain; }

    /** Answer the alias for rdfs:range in daml namespace */
    @Override
    public Property range() { return range; }

    /** Answer the alias for rdfs:label in daml namespace */
    @Override
    public Property label() { return label; }

    /** Answer the alias for rdfs:comment in daml namespace */
    @Override
    public Property comment() { return comment; }

    /** Answer the alias for rdfs:seeAlso in daml namespace */
    @Override
    public Property seeAlso() { return seeAlso; }

    /** Answer the alias for rdfs:isDefinedBy in daml namespace */
    @Override
    public Property isDefinedBy() { return isDefinedBy; }

    /** Answer the RDF Property for the DAML sameIndividualAs property on instances */
    @Override
    public Property sameIndividualAs() { return sameIndividualAs; }

    /** Answer the RDF Property for the DAML differentIndvidualFrom property on instances */
    @Override
    public Property differentIndividualFrom() { return differentIndividualFrom; }

    /** Answer the alias for rdfs:Property in the daml namespace.  From 2001/03 onwards, it is preferable to use either DatatypeProperty or ObjectProperty. */
    @Override
    public Resource Property() { return Property; }

}

redpajama_set_name: RedPajamaGithub


text:
Q: Ajax method call on Ajax File Upload button I'm using ajax file upload to upload multiple files directly stored in my dropbox account without letting them to store on any local directory or folder. For that I'm using ajax call method. But somehow I'm not able to run that ajax call when i click on upload button to upload files.
Below is the code for uploading multiple files.
Upload.aspx

                            <%--<asp:FileUpload ID="FileUpload1" runat="server" />

--%>
                        <asp:AjaxFileUpload ID="AjaxFileUpload1" runat="server" OnUploadComplete="AjaxFileUploadEvent" />

redpajama_set_name: RedPajamaStackExchange


text:
Writing · Writing Process
Do You Listen to Music While Writing?
01/08/2018 07/08/2018 Debbie Johansson6 Comments
Whenever I write I usually tend to listen to white noise. I find listening to music with lyrics easily distracting as the words that I'm hearing tend to clash with the words that are forming in my head. This is why I tend to listen to such music between writing sessions, as I find music can be a great motivator and can also help if you are experiencing writer's block.
While writing my most recent WIP, I managed to make a couple of changes. One was to listen to the sounds of nature instead of always listening to white noise. My nature of choice was listening to waves crashing upon the beach, one of my favourite sounds since childhood. I've discovered that not only can some of these sounds be relaxing while you write, but some can also help bring about a sense of atmosphere to our scenes.
The other change I made was listening to certain songs that fitted in well with my WIP's themes and characters. This allowed me to know my characters better, what their motivations were and helped to develop my plot. This would explain why a lot of writers tend to create playlists for their novels.
During the writing of my WIP, I listened to the album A Beautiful Lie by Thirty Seconds to Mars. Almost every song on that album resonated with me one way or another, for both my characters and for myself on a more personal level during the time I was writing. The lyrics from the title song became embedded into my head, not only for the song itself, but because it was suitably suited to my story. The Kill in particular really stuck and how could I not go past the references to The Shining in this video? 😉
Just as much as we need to experiment with our writing, there are times when we may also need to experiment with our entire writing process. Listening to a variety of music and sounds, as well as creating playlists can all become a part of that creative process.
Do you listen to music while writing or do you prefer silence? Have you found music helpful with your writing process? Do you create playlists for your novels?
Image courtesy of Pixabay
Back to the 80s: Z is for ZZ Top.
Here we are folks, we have finally made it to the end of my Back to the 80s Challenge (bring out the bubbly, it is almost Christmas after all)! Honestly, there have been some occasions when I didn't think I would actually reach this point and felt like throwing it in a few times, but when I start something I like to see it finished.
This was the first time I set myself a blog challenge and I don't think I'll be in a hurry to do another, but never say never I guess. Anyway, thanks for sticking with me; it certainly has been testing my memory and has been a great help in researching the pop culture of the time for some of my stories.
Formed in 1969, ZZ Top had released three albums by 1973 and performed sold out concerts in the U.S. They released three more albums in the 1970s and had their first European tour in 1980. In 1983, they released the album Eliminator, which was highly successful and sold more than ten million copies. It included such hits as 'Legs', 'Gimme All Your Lovin" and 'Sharp Dressed Man'. The videos for some of these songs helped the band win their first MTV Video Music Awards. Released in 1985, their next album Afterburner became the band's highest charting album and many of its singles became Top 40 hits.
The band went on to release six more albums, and in 2004 were inducted into the Rock and Roll Hall of Fame. They continue to perform to this day. Their trade mark beards and fluffy guitars make them one of the more memorable bands of the 1980s.
If you're a blogger, have you ever set yourself a challenge? What other bands of the 1980s that begin with the letter Z can you think of?
Enjoy this article? Subscribe to my blog and never miss a post. You can also follow me on Twitter, Facebook, Instagram and Pinterest.
Back to the 80s: Y is for Yazoo.
Another week in and as we're nearing the end of another year, so too are we nearing the end of my Back to the 80s Challenge. This week, we're looking at the letter Y and I'll be focusing on a synthpop duo.
Formed in England in 1981, Yazoo consisted of Alison Moyet on vocals and Vince Clarke on keyboards. Alison placed an ad in the hope of forming a band and it was answered by Vince Clarke, once a member of Depeche Mode.
The song 'Only You' was released in 1982 and reached No.2 in the U.K singles charts. The song 'Don't Go' was released the same year and reached No.3. Their first album, Upstairs at Eric's was also released in 1982 and reached No.2 in the U.K album charts. Yazoo became known in the United States as Yaz and their song 'Situation' had become a hit, making it into the Billboard Hot 100.
In 1983, they released the single 'Nobody's Diary', which reached No.3 in the U.K charts. It was not long after the release of the single, that the duo announced they had disbanded due to a clash of personalities and lack of communication between the pair. Despite the split, their second album, You and Me Both, was released later that same year and reached No.1 in the album charts. Alison Moyet has an amazing voice and after Yazoo, she went on to have a successful solo career.
Other bands formed or who had hits in the 1980s starting with the letter Y include:- Yothu Yindi, Yello.
What other bands of the 1980s that begin with the letter Y can you think of?
Back to the 80s: X is for XTC.
It's the end of another week and once again, it's time for my Back to the 80s Challenge. We are now down to the last three and it hasn't always been easy coming up with band names. These last few have left me struggling sometimes to even to come up with more than one band name. This week is a perfect example of that!
XTC were formed in England in 1972 and their debut album, White Music, was released in 1978. It wasn't until their third album, Drums and Wires was released in 1979, that they had their first hit single, 'Making Plans for Nigel'. Their fourth album, Black Sea, was released in 1980. This album contained the hit single 'Generals and Majors', which made the U.K Top 40 and the album reached No.1 in Australia. In 1982, they released their fifth album and the single 'Senses Working Overtime' made the Top 10 in the U.K.
In the early 1980s, the band embarked on a world tour, but had to cancel due to health reasons for one of the band members. They then became a studio band and released six more albums in the 1980s, including two under their alter-ego, 'The Dukes of Stratospher'. Over the years, despite issues with band members and their record labels, they released at least three more albums, but eventually disbanded in 2006.
'And all the world is biscuit shaped, it's just for me to feed my face' – it sounds silly I know, but I always liked that line! 😉
What are some silly song lyrics that you like listening to? What other bands of the 1980s that begin with the letter X can you think of (it's got me stumped)?
Back to the 80s: W is for Wang Chung.
01/12/2017 30/11/2017 Debbie Johansson1 Comment
Another week in and just as fast as Christmas is approaching and catching me unawares, so too are we getting closer to the end of my Back to the 80s Challenge. As we are down to the last four, I'll be doing one every week in time for Christmas to see off 2017.
Wang Chung were formed in the U.K in 1980. The term 'Huang Chung' means 'yellow bell' in Mandarin and the band initially used this as their name, only later to change it to Wang Chung for better translation in English. The band signed a two record deal in 1981 and their first album was released a year later. In 1982, while working on a new album, they released the single 'Dance Hall Days', which failed to chart. It was at this point that their contract was cancelled and they signed up with an American label.
Their second album Points of the Curve was released in 1984 and had two successful hits, 'Don't Let Go' and 'Dance Hall Days' (a re-recording of the original version). In 1985, they released the soundtrack to the movie To Live and Die in L.A., which became their third album. Their fourth album, Mosaic was released in 1986, which contained their biggest hits 'Everybody Have Fun Tonight' and 'Let's Go!', reaching No.2 and No.9 in the U.S. respectively. Wang Chung released their fifth album, The Warmer Side of Cool in 1989, where they had a minor hit, but overall, the album was considered a disappointment. Band members then went on to other projects and eventually disbanded in 1990.
As pointed out in some of the comments on YouTube for this video, this clip needs to come with a seizure warning. And yes, I'd hate to be the one responsible for the editing! 😉
Other bands formed or who had hits in the 1980s starting with the letter W include:- Wham, Was Not Was, Wet, Wet, Wet, Warumpi Band, White Snake.
Have you been caught off guard at how quickly Christmas is almost upon us? What other bands of the 1980s that begin with the letter W can you think of?
Back to the 80s: V is for The Vapors.
Once again we're back for another round in my Back to the 80s Challenge and gradually working our way down to the end of the list.
Before jumping in though, recently I was extremely fortunate to see my all time favourite band of any era – Midnight Oil. They were, as expected, absolutely brilliant and I haven't come down from the ceiling as yet (could take a few days). Anyway, back to the challenge and this week we're down to the letter V.
Formed in the UK in 1978, The Vapors were discovered by one of the band members of The Jam and were offered to support them during one of their tours a year later. Their first single was released in 1979, but failed to chart. Their second single 'Turning Japanese', reached the top three in the UK, as well as becoming a hit in Canada, Australia and New Zealand. The song appeared on their debut album New Clear Days. Two more singles later made it into the UK Singles Chart and they released another album in 1981. The band broke up in 1982, believed to be due to a lack of support from their record label.
Other bands formed or who had hits in the 1980s starting with the letter V include:- Van Halen.
What other bands of the 1980s that begin with the letter V can you think of? Have you seen any good bands recently?
Back to the 80s: U is for U2
It's time once again for my Back to the 80s challenge and now that we're getting closer to the end, we're reaching the letters of the alphabet that really will be a challenge!
This time around is a band that became a huge success in the 1980s and another band that I was fortunate to see live. Back in the day, they were one of my favourites, but personally, they reached a point where musically, I eventually lost all interest (hey, it happens sometimes).
U2 were formed in Dublin, Ireland in 1976 and released their first album Boy in 1980. The album received positive reviews and they released the album October a year later. The album War was released in 1983 and the single 'New Year's Day' was to become the band's first hit outside of the U.K. They toured Europe and the U.S, which resulted in their live album Under a Blood Red Sky. The album Unforgettable Fire was released in 1984, which was successful in the U.S and became No.1 in the U.K. The single 'Pride (In the Name of Love)', became their biggest hit and the band performed at the Live Aid concert in 1985, with a television audience estimated of 2 billion people. It would help establish what Rolling Stone magazine labelled as 'the band of the 80s' that same year.
Their fifth album, The Joshua Tree, was released in 1987 and was critically acclaimed. It went to No.1 in over twenty countries and won two Grammy Awards. A year later, the album Rattle and Hum was released and reached No.1 world wide. Over the years, U2 would go on to release eight more albums, tour extensively, become one of the most best-selling artists in history and be inducted into the Rock and Roll Hall of Fame.
This song was my favourite from their very early years and I recall a different clip. But oh dear, Bono's hair in this one – so very 80s! 😉
Other bands formed or who had hits in the 1980s starting with the letter U include:- Ultravox, Uncanny X-Men, UB40, Underworld.
Have you ever lost interest in certain bands when they change musical direction? What were some of your favourite bands during the 1980s? What other bands of the 1980s that begin with the letter U can you think of?

redpajama_set_name: RedPajamaCommonCrawl


text:
jeff-wise
Jeff Wise Is Here to Chat About His Flight MH370 Disappearance Theory
J.K. Trotter · 02/24/15 02:00PM
Anyone obsessed with the disappearance of Flight MH370 knows the name of Jeff Wise, a private pilot and science writer who has frequently appeared on CNN to track new developments in the search for the missing plane. Today he's here to chat with Gawker readers about his personal theory—detailed in a 95-page Kindle Single and excerpted in New York magazine—for how the passenger jet vanished without a trace on March 8, 2014. It involves bogus flight data, Russian hijackers, and a remote facility in Kazakhstan (among others things).


Protecting loved ones and valuable possessions is a chief concern that weighs heavily on our minds. Although recent data suggests that property crimes are declining at a crawling pace, as of 2015 7.6% of households in the United States experienced at least one form of property victimization or another. It's natural to want to have a sturdy door and an equally capable lock to keep it in place to prevent this from happening to you.
Keyless Locks: Are Keyless Door Locks Secure?
Keyless door locks have been gaining popularity in recent years, especially with widespread smartphone use allowing remote control and individual customization. While they're certainly more technologically advanced, the question remains – are keyless door locks secure, or rather, are they more secure than the tumbler lock most of us still rely on?
Not having an actual physical lock to pick is the keyless lock's greatest advantage. A skilled lock picking expert can have a standard tumbler lock open in less than a minute.
Even more frightening is the recent practice of lock bumping where the burglar uses a set of bumper keys to gain entry into the locked space almost as efficiently as they would with the corresponding key, leaving no signs of forced entry behind.
Not having a key also means that one isn't relying on a spare if the first one happens to get lost. You wouldn't believe how many people still hold onto the cliché of putting their spare key inside a potted plant or under the rug, practically inviting the thief to come in and take his pick.
No one has more than one or two spares anyway, but what if you need more? With a keyless lock, each family member, guest or people like caretakers, dog walkers etc. get their own code / gain access with their fingerprint, eliminating the need for more keys.
More importantly, from a security standpoint is the fact that once it's no longer desirable for someone to have a valid code, deleting it is as easy as pressing a sequence of buttons, eliminating them as a potential threat and saving you a great deal on lock replacements.
Installing a keyless lock is also a smart way of keeping track of who's been using the door and at what time. Some advanced models have built-in software which keeps a log that displays the passkeys that were used to gain entry, as well as timestamps of when this happened.
Most keyless locks are run by batteries, meaning that they won't be affected by a power outage. Usually you're given ample warning to replace them, and an alternative means of entry, like a jumper box, if you forget to do that. If an outage does occur, you won't need to fumble in the dark for a key anymore since your new lock's keypad is nice and bright.
While possible, bypassing a keyless lock is harder to do than a conventional one. When they detect signs of tampering, most keyless locks trigger an audible alarm which alerts you to the presence of danger and will send most criminals scurrying. More advanced models are mini security systems in their own right, sending out information to the police whenever a break-in is in progress.
As with anything, of course there are! Biometric systems can be bypassed, those long eight-digit passwords can be easily forgotten, and there's nothing short of a comprehensive alarm system stopping a burglar from eschewing your doors altogether and getting in through the window. Keyless or not, a lock is only as sturdy as its internal components.
The main takeaway, however, is that in general, keyless door locks do in fact provide more security to the door they're installed on, and are definitely much more convenient than their traditional counterparts. There's a wide variety of locks to choose from, each relying on one of a handful of security measures or combinations thereof.
Reading up on the newest advances in lock technology, getting to know some of the best locks out there, and taking the time to research which kind of lock will be best suited for your security needs, are all sensible first steps you should take before getting a new kind of lock.


'Personal Branding' through social media is becoming more and more important in today's society. How does your self-perception match with the perception of others? Through your website and social media such as Linkedin, Twitter, Facebook and Youtube you can build and develop your personal profile in the virtual world. Developing a video presenting myself was one of my key activities, I facilitated last month.


text:
\section{\label{sec:Introduccion}Introduction}

In recent years, there has been significant progress in understanding the properties of neutrinos, most notably, since 2012 the results of the reactor neutrino experiments Daya Bay~\cite{DayaBay}, Reno and Double Chooz~\cite{DoubleCHOOZ} have determined that the mixing angle $\theta_{13}$ is nonzero with a high level of significance. The current degree of development of neutrino detection technology is close to making a reality to non-intrusively monitor the operational status, power level and fissile content of a nuclear reactor in real time using detectors placed at distances of a few tens of meters.

Monitoring nuclear reactors through its antineutrino flux is a complimentary and promising new tool for supervising the operations of nuclear plants, which are bound to operate according to protocols established by the International Atomic Energy Agency (IAEA). This agency is responsible for ensuring that nuclear reactors world wide operate legally, preventing the diversion of fissile material to activities which could lead to the manufacture of weapons.

Many research groups worldwide (~\cite{SONGS}-\cite{DANSS}) have studied this application aiming at adding antineutrino detection to the techniques used to implement reactor safeguards. In a medium term plan (5 to 8 years) IAEA~\cite{IAEA_workshop} has proposed that antineutrino detectors for safeguard applications should be able to provide information on the thermal power, fissile content and operational status of reactors while deployed aboveground in a compact volume to minimize its intrusiveness with the nuclear power plant operations. The SONGS1 experiment~\cite{SONGS} using a Gd loaded liquid scintillator detector, deployed at 25 m from the reactor core of the San Onofre Nuclear Generation Station, successfully proved that the reactor ON/OFF cycle and the thermal power stability of a reactor can be measured using a compact and simple detector. PANDA [4], lead by Tokyo University, used a segmented plastic scintillator detector with modules wrapped with Gd coated sheets in between. This type of detector makes it possible to use information of the event topology to tag antineutrino events and to discriminate them from backgrounds such as fast neutrons. Furthermore, it can be transported and operated easily inside a compact vehicle, and has the advantage that unlike the liquid scintillators, is non-flammable.

M\'exico has two nuclear fission reactors at the Laguna Verde Nuclear Power Plant (LVNPP), which operates commercially since 1990 (Unit 1) and 1995 (Unit 2). This is the only nuclear power plant in the country and generates about 5\% of its total electric power production. In this work we calculate the antineutrino flux produced by these reactors and give some estimates of the number of events expected in a generic plastic scintillator detector located at a distance of 100 m from the reactor cores. Knowledge of the antineutrino flux produced by a particular reactor is an important step towards its monitoring using this method.

While abundant literature exists about the calculation of neutrino fluxes from pressurized water reactors (PWR)~\cite{literature}, much fewer information is available about neutrino production at boiling water reactors (BWR) (See for example~\cite{Nakajima}). These two reactor types operate under the same basic physical principles regarding nuclear fission, but differences in their operational procedures may effect differently the neutrino flux they produce, as well as its evolution along the reactor fuel cycle.

This paper is organized as follows: in section \ref{sec:CNLV} main technical data on the LVNPP and its reactors are detailed. In section \ref{sec:DRAGON} a description about the production of antineutrinos from nuclear reactors is given, and the calculation of antineutrino flux is presented. In Section \ref{sec:Flujo} parameters and characteristics of the DRAGON simulation code used to calculate fission rates of four major fissile isotopes for this paper are described. Section \ref{sec:eventos} shows the event rates or interactions that are expected to be observed with a 1 ton plastic scintillator detector placed at 100 meters from the LVNPP reactors. Finally, section\ref{sec:Conclusiones} presents the conclusions.

\section{\label{sec:CNLV}The Laguna Verde Nuclear Power Plant (LVNPP)}

The LVNPP is located in the municipality of Alto Lucero, Veracruz, M\'exico. This plant has two twin units, each equipped with a BWR-5 second generation reactor with a Mark II containment design, supplied by General Electric with a capacity of 2027 MWth, and net electrical output of 805 MWe. Both reactors operate with enriched uranium as fuel, and demineralized water as moderator and coolant. It is the only nuclear power plant in the country and generates about 5\% of the total electric power production in M\'exico~\cite{reporteIAEA}.

Each nuclear reactor core can be approximately represented by a cylinder $\sim$4 m in height and 4 m in diameter containing 444 fuel assemblies and 109 control bars arranged as shown in Fig. \ref{fig:carga_inicial_3colores}. A fuel assembly is a square prism with sides of $\sim$13 cm and 4 m in height, containing an array of fuel rods (configurations of 8x8, 10x10 or 12x12 have been either used or considered). Within a given fuel assembly some of the rods contain uranium oxide (UO$_2$) with various levels of enrichment, others contain a mixture of UO 2 with gadolinium oxide (Gd$_2$O$_3$) at varying concentrations, and some of them are hollow in order to allow the flow of the refrigerant through them. Combining rods with different levels of enrichment and Gd$_2$O$_3$ concentrations permits to adjust the properties of the medium for the production, absorption and diffusion of neutrons differently at various location across the core.

\begin{figure}[t]
\centering
\includegraphics[width=0.4\textwidth] {initial_fuel_load.png}
\caption{\small{Schematic of a cross section of one of the LVNPP reactor cores \cite{folletoCNLV}. The "red" assemblies (0.711\%) are located on the perimeter of the reactor core, while the "blue" assemblies (1.76\%) are arranged in the central area. There are 109 control bars represented as crosses in the figure.}}
\label{fig:carga_inicial_3colores}
\end{figure}

\section{\label{sec:DRAGON}DRAGON simulation of the reactor core}

We used the numerical simulation code DRAGON~\cite{Pagina_DRAGON} with the modifications described in~\cite{modifica_DRAGON} to implement a simulation for the LVNPP reactors and extract the time evolution of the fission rates (number of fissions per second) of each of the main fisile isotopes in the core. Several research groups worldwide have implemented this simulation for PWR reactors, aiming at the same objective~\cite{fiss_frac_DRAGON}. The code solves the neutron transport equations of individual fuel assemblies, whose detailed composition is given as an input. The overall behaviour of neutrons across the core can be calculated by summing over the various types of assemblies that compose a given core configuration.

As described in section \ref{sec:CNLV}, a geometry with 444 fuel assemblies with 3 different types of $^{235}$U enrichment was considered. The initial fuel load that was assumed in this work is that shown in Fig. \ref{fig:carga_inicial_3colores}. Note that in this model no assembly contains plutonium at the beginning of the operation cycle.

\begin{figure}[b]
\centering
\includegraphics[width=0.48\textwidth] {blue_assembly.png}
\caption{\small{Arrangement of fuel rods for blue assembly (half enrichment). Left: DRAGON code output. Right: Bar type (see Table \ref{tab:ensamble_azul_tabla}). Notice that initially there are no fuel bars with Pu.}}
\label{fig:ensambleycelda}
\end{figure}

In Fig. \ref{fig:ensambleycelda}, we illustrate a single fuel assembly (in this case with a 10x10 rod configuration) corresponding to one with average enrichment of 1.76\% (blue assembly). The dimensions of a single unit cell, (the place occupied by a single fuel rod) are shown in Fig. \ref{fig:celda_unitaria}. The three types of assembly (red, yellow and blue) share the same geometry, however, the composition the fuel rods within a given assembly is, in general, different. The number of assemblies of each type, $N_A$ is: $N_{red} =68, N_{yellow}=280$ and $N_{blue}=96$, totaling 444.

We considered eight different fuel rod compositions, labeled $CX$, with $X = 0, 1, 2, 3, 4, 5, 6, G$, and used them to construct the various assemblies with the desired $^{235}$U enrichment and Gadolinium concentration. Only fuel rods of type G contain Gadolinium. Table \ref{tab:barras_por_ensamble} shows the number of fuel rods of each type that are used to build each of the three assemblies. As an example, Table \ref{tab:ensamble_azul_tabla} shows how we constructed the blue assembly.

\begin{table}[h]
	\begin{center}
		\begin{tabular}{|c|c|c|c|c|c|c|c|c|c|}
		\hline
		Assembly & C0  & C1 & C2 & C3 & C4 & C5 & C6 & CG \\

		\hline
		Red & 92 & 0 & 0 & 0 & 0 & 0 & 0 & 0 \\
		\hline
		Blue & 59 & 0 & 0 & 3 & 4 & 6 & 8 &12\\
		\hline
		Yellow & 34 & 9 & 19 & 0 & 0 & 0 &0 &30\\
		\hline

		\end{tabular}
		\caption{\small{Number of fuel bars of type CX for each assembly. There is a total of 92 bars for each assembly.}}
		\label{tab:barras_por_ensamble}
	\end{center}
\end{table}

\begin{figure}[t]
\centering
\includegraphics[width=0.25\textwidth] {unit_cell.png}
\caption{\small{Cross section of a single unit cell. A fuel bar (in red) with a zircaloy cladding (white) immersed in demineralized water as moderator. A complete assembly is formed by 92 of these cells. The values for R1, R2 and L are described in Table \ref{tab:parametros_simulacion}}}
\label{fig:celda_unitaria}
\end{figure}

Table \ref{tab:parametros_simulacion} lists the values used for the various parameters required by the simulation. Tests showed a small dependence of the fission rates on variations of the coolant, moderator and fuel temperatures, while maintaining the thermal power constant.

A simulation was run for each of the three types of assembly (red, blue or yellow in Fig. \ref{fig:carga_inicial_3colores}), providing the fission rates $f_i^{(CX;A)}$ for each type of fuel rod, and for each one of the fissile isotopes $i=1,2,3,4$  ($^{235}$U, $^{238}$U, $^{239}$Pu and $^{241}$Pu, respectively).

To obtain the fission rates for a given assembly, $f^A_i$, we multiply the fission rate for each type of fuel rod times the number of rods of its type in the assembly, $N_{rods}$, and sum over all fuel rod types in the assembly, i.e:

\begin{equation}
f_i^A = \sum_{CX\in A} N_{rods} (CX;A) f_i^{(CX;A)}
\end{equation}

Finally, to calculate the fission rates of isotope $i$ in the complete reactor core, $f_i$ (Fig. \ref{fig:fissionrates}), we multiply the number of assemblies of each type $A$, times the corresponding
fission rates for that assembly:

\begin{equation}
f_i=\sum_{A} N_Af_i^A
\end{equation}

\begin{table}[t]
	\begin{center}
		\begin{tabular}{|c|c|c|c|c|c|c|}
		\hline
		Rod type & \# of rods & $^{234}$U & $^{235}$U & $^{238}$U & O$_{16}$ & Gd \\
		   & & (\%)&(\%) &(\%) &(\%) &(\%)\\
		\hline
		C0 & 59 & 0.005 & 0.627 & 87.517 & 11.852 & -\\
		\hline
		C3 & 3 & 0.029 & 2.468 & 85.651 & 11.852 & -\\
		\hline
		C4 & 4 & 0.029 & 2.821 & 85.298 & 11.852 & -\\
		\hline
		C5 & 6 & 0.029 & 3.173 & 84.945 & 11.852 & - \\
		\hline
		C6 & 8 & 0.029 & 3.482 & 84.637 & 11.852 & - \\
		\hline
		CG & 12 & 0.028 & 3.142 & 79.691 & 11.933 & 5.206\\
		\hline
		\end{tabular}
		\caption{\small{Isotopic composition of fuel bars for blue assembly in Fig.\ref{fig:carga_inicial_3colores}.  UO$_2$ and UO$_2$-Gd$_2$O$_3$ bars with an overall average enrichment of 1.76\% of $^{235}$U (relative to the total U). Fuel rods with Gd admixture have an enrichment of 5.2\% (in total) and 3.792\% (relative to U).}}
		\label{tab:ensamble_azul_tabla}
	\end{center}
\end{table}

The simulation was run simulating time intervals of 5 days of evolution of the nuclear reactor core until complete a full operation cycle of 400 days.

As is expected for an initial load without plutonium, the fission rates of $^{239}$Pu and $^{241}$Pu start at zero and rapidly grow to become comparable to those of the U isotopes within a few weeks of operation. A more realistic situation should consider that between two fuel reloads, there will always be some remnant of plutonium inside the reactor, because when this action is performed, only a fraction of the spent fuel is replaced by new material.

\begin{table}[b]
	\begin{center}
		\begin{tabular}{|l|r|}
		\hline
		Thermal Power (of each reactor) & 2027 MWth\\
		\hline
		Specific power (of each reactor) & 20.43 MW/Ton\\
		\hline
		Moderator & Demineralized water\\
		\ \ \  Temperature & 600 K\\
		\ \ \  Density & 0.720 g/cm$^3$\\
		\hline
		Coolant & Demineralized water\\
		\ \ \  Temperature & 400 K\\
		\ \ \  Density & 0.720 g/cm$^3$\\
		\hline
		Fuel assemblies  & 444\\
		\ \ \  Red assemblies & 68\\
		\ \ \  Blue assemblies & 96\\
	    \ \ \  Yellow assemblies & 280\\
		\hline
		Single unit cell (L$\times$L)& 1.295 cm$\times$1.295 cm\\
		\hline
		Fuel bars per assembly & 92\\
		\ \ \  Composition & UO$_2$/UO$_2$-Gd$_2$O$_3$\\
		\ \ \  Cladding & Zircaloy 2\\
	    \ \ \  Zircaloy density & 5.821 g/cm$^3$\\
		\ \ \  Zircaloy temperature & 600 K\\
		\ \ \  Fuel temperature & 900 K\\
		\ \ \  Fuel density  & 10.079 g/cm$^3$\\
		\ \ \  Fuel bar radius (R1)& 0.438 cm\\
		\ \ \  Zircaloy cladding radius (R2)& 0.513 cm\\
		\ \ \  Fuel bar height  & 400 cm\\
		\hline
		Coolant pipes per assembly & 2\\
		\ \ \  Composition & Zircaloy 2\\
		\ \ \  Pipe radius (occupied by water) & 1.0 cm\\
		\ \ \  Pipe radius (occupied by zircaloy) & 1.2 cm\\
		\hline
		\end{tabular}
		\caption{\small{Parameters of the BWR core used in the simulation with DRAGON code.}}
		\label{tab:parametros_simulacion}
	\end{center}
\end{table}

\begin{figure}[h]
\centering
\includegraphics[width=0.5\textwidth] {fiss_rates.png}
\caption{\small{Fission rates (normalized) obtained with DRAGON for the 4 main fissile isotopes in the 444 fuel assemblies that make up the core of a BWR-5 of 2.027 GWth like the LVNPP reactor.}}
\label{fig:fissionrates}
\end{figure}

\section{\label{sec:Flujo}The antineutrino flux}

The power output of a nuclear reactor originates from the energy released in the fission of heavy elements, such as uranium and plutonium, into lighter fission fragments which are often unstable. The beta decay, $(A,Z)\rightarrow (A,Z+1)+e^-+\bar{\nu}_e$, of the fission fragments produces a large number of electron antineutrinos $\bar{\nu}_e$ which are emitted isotropically from the core.
During the fuel "burning" process, uranium isotopes breed $^{239}$Pu and $^{241}$Pu. The latter may in addition to the $^{235}$U undergo a fission process only with slow (thermal) neutrons, while $^{238}$U is fissionable by fast neutrons only. The decay of $^{239}$Pu produces substantially less antineutrinos than the decay of $^{235}$U in the same energy range, therefore during a typical reactor fuel cycle, the amount of antineutrinos decreases as uranium content decreases and the concentration of plutonium increases.

Each fission releases on average $\sim$200 MeV of energy and produces $\sim$6 $\bar{\nu}_e$ ($\sim 3$ beta decays per fission fragment), with energies below $\sim$10 MeV. This sets the number of antineutrinos emitted by a typical reactor to $\sim2\times10^{20} \bar{\nu}_e/s$ per GWth of thermal power. The energy spectrum of the antineutrinos depends on the fuel composition at a given time ($^{239}$Pu antineutrinos are slightly less energetic than those of $^{235}$U fission products).

The production of reactor antineutrinos is not exclusively through beta decay of the fission fragments of the four main fissile isotopes ($^{235}$U, $^{238}$U, $^{239}$Pu and $^{241}$Pu).The neutron capture in $^{238}$U(n,$\gamma$) $^{239}$U also generates this particles in a process that contributes about 17\% of the total antineutrino flux. This process occurs when a nucleus of $^{238}$U captures a neutron, leading to the following reaction: $^{238}$U+n$\rightarrow ^{239}$U $\rightarrow ^{239}$ Np $\rightarrow ^{239}$Pu, and produces two antineutrinos through two beta decays of $^{239}$U. This process occurs at a rate of $\sim$0.6 per fission, and produces antineutrinos with energies below 1.3 MeV.

There is no established experimental method for measuring the flux of very low energy antineutrinos. For a technological application such as reactor monitoring, only antineutrinos with energies above the threshold of the Inverse Beta Decay (IBD) reaction on free protons (E$_{\nu}$ \textgreater 1.8 MeV) can be realistically considered. IBD interactions of neutrinos on free protons can be identified through the correlation of the prompt positron signal and a delayed neutron capture signal. In general, the spectrum of the antineutrinos from a nuclear reactor detected via IBD has a peak between 3.5 and 4 MeV. Since the number of emitted antineutrinos and their average energy depend on the amounts of $^{235}$U, $^{238}$U, $^{239}$Pu and
$^{241}$Pu isotopes present in the core, the measured energy spectrum provides a direct image of the fuel composition of the reactor core at a given time.

Let us now consider the antineutrinos emitted by one of the reactors at the LVNPP. Ignoring the neutron capture contribution, the antineutrino flux $\Phi_i$ above 1.8 MeV can be calculated from the fission rates $f_i(t)$, and the antineutrino energy spectrum $S_i(E_{\bar{\nu}})$ of each isotope $i$, where $i = 1,2,3,4$ corresponds to each of the main fissile isotopes of the reactor core: $^{235}$U, $^{238}$U, $^{239}$Pu and $^{241}$Pu.

Assuming neutrinos are emitted isotropically, using a sphere of radius $R$, the flux at a time $t$ for each isotope $i$ is calculated as:

\begin{equation}
\Phi_i(E_{\bar{\nu}},t) = \frac{1}{4 \pi R^2} S_i(E_{\bar{\nu}}) f_i(t) ,
\label{eq:Flujoneutrinos}
\end{equation}
with $R$ the distance from the reactor core to the detector.

\begin{figure}[b]
\centering
\includegraphics[width=0.45\textwidth] {espectro_MF.png}
\caption{\small{Energy spectra of the emitted antineutrinos per fission of $^{235}$U, $^{238}$U, $^{239}$Pu and $^{241}$Pu. The dotted line at 1.8 MeV indicates the threshold for the Inverse Beta Decay (IBD) process.}}
\label{fig:Mueller_Fallot}
\end{figure}

In our calculation of the antineutrino flux, we have used the new predictions of the energy spectra including the effect of the reactor antineutrino anomaly, as reported by~\cite{anomaly}, \cite{Fallot} and \cite{Mueller}. The antineutrino energy spectra $S_i(E_{\bar{\nu}})$ between 1.8 and 8 MeV are shown in Fig. \ref{fig:Mueller_Fallot}. For the purposes of reactor monitoring, the effect of this anomaly can be ignored as long as only comparisons between the relative changes of the spectrum throughout the reactor operation cycle are made.

Fig. \ref{fig:flujos} shows the antineutrino flux for each of the main fissile isotopes of one of the reactors in the LVNPP, at day 5 (top) and then at day 200 (bottom), in the latter the flux can be considered as stable. The total flux (the sum of the four isotopes) for each time period is also shown in the gray curve in this figure. The total flux at day 200 is shown in table \ref{tab:flujodia200}.

\begin{figure}[t]
\centering
\includegraphics[width=0.5\textwidth] {fluxday5.png}\\
\includegraphics[width=0.5\textwidth] {fluxday200.png}
\caption{\small{Antineutrino flux produced by the fission of the 4 main fissile isotopes at 100 meters from one of the LVNPP reactors of 2.027 GWth at day 5 (up) and 200 (bottom) of operation. The gray curve (on top) is the total flux.}}
\label{fig:flujos}
\end{figure}

Two systematic uncertainties are associated with the calculation of the antineutrino flux: the error due to the energy spectra of antineutrinos $\delta(S(E_{\bar{\nu}}))$, and an error $\delta (P_{th})$ associated with fluctuations in the thermal power of the reactor core, assumed to be 5\% along one fuel cycle. The total error is the sum in quadrature of these uncertainties. The uncertainties in the antineutrino spectra are taken from Refs.~\cite{Fallot} and~\cite{Mueller}, and are of the order of 2-5\% for the dominant parts of the spectra from $^{235}$U,$^{239}$Pu, and $^{239}$Pu, and between 10-17\% for the dominant
part of the spectrum from $^{238}$U.

The total flux per reactor at day 200 from our calculation is compared in Fig. \ref{fig:flujoXsec200} to that obtained according to the parametrization suggested by Vogel and Engel~\cite{Xsec_DBI_vogel}, setting the fission rates of the four main fissile isotopes to these output by the simulation (2.7 $\times 10^{19}$ fis/s for $^{235}$U, 7.7 $\times 10^{18}$ fis/s for $^{238}$U, 2.8 $\times 10^{19}$ fis/s for $^{239}$Pu, and
1.5 $\times 10^{18}$ fis/s for 241 Pu). The two calculations agree well within the assumed uncertainties.

Spent fuel is stored temporarily in a nearby place to the reactor core and has a very small contribution to the antineutrino flux below the IBD reaction threshold, and was not considered for the calculation in this work.

\begin{table}[t]
	\begin{center}
		\begin{tabular}{|l|c|c|}
		\hline
		E [MeV] & $\Phi_{total}$ [MeV$^{-1}$ s$^{-1}$cm$^{-2}$]  & $\delta$(sist) [\%] \\
		\hline
		\hline
 1.800 & 6.921E+10 & 7.2\\
 2.048 & 6.192E+10 & 3.6\\
 2.296 & 5.185E+10 & 3.6\\
 2.544 & 4.304E+10 & 3.7\\
 2.792 & 3.634E+10 & 3.7\\
 3.040 & 3.052E+10 & 3.7\\
 3.288 & 2.542E+10 & 3.7\\
 3.536 & 2.066E+10 & 3.8\\
 3.784 & 1.671E+10 & 3.8\\
 4.032 & 1.336E+10 & 3.9\\
 4.280 & 1.045E+10 & 4.0\\
 4.528 & 8.026E+09 & 4.0\\
 4.776 & 6.147E+09 & 4.1\\
 5.024 & 4.841E+09 & 4.2\\
 5.272 & 3.761E+09 & 4.3\\
 5.520 & 2.871E+09 & 5.2\\
 5.768 & 2.157E+09 & 5.4\\
 6.016 & 1.584E+09 & 5.5\\
 6.264 & 1.179E+09 & 5.6\\
 6.512 & 8.900E+08 & 5.8\\
 6.760 & 6.692E+08 & 5.9\\
 7.008 & 4.752E+08 & 7.0\\
 7.256 & 3.027E+08 & 7.4\\
 7.504 & 1.881E+08 & 7.8\\
 7.752 & 1.210E+08 & 8.4\\
 8.000 & 6.763E+07 & 9.8\\
\hline
		\end{tabular}
		\
		\caption{\small{Total antineutrino flux at day 200 of one of the reactors of the LVNPP, at a location of 100 m from the reactor core.} }
		\label{tab:flujodia200}
	\end{center}
\end{table}

\section{\label{sec:eventos}Event Rates}

Although the IBD reaction has a very small cross section ($\sim$10$^{-43}$cm$^2$), the enormous flux emitted by a nuclear reactor allows the signal to be observed with a relatively small detector located a few tens of meters from the reactor core. The total IBD cross-section as a function of the neutrino energy is shown in Fig. \ref{fig:flujoXsec200} (right scale). Here we consider 1 ton of polyvinyl-toluene (PVT) plastic scintillator located at 100 m from each of the reactor cores, similar to the detector considered in~\cite{PANDA}.

The number of IBD interactions associated with neutrinos from isotope $i$, emitted with energies between $E_{min}$ and $E_{max}$, and occurring in a time interval $\Delta t$ ($\Delta N_{\textrm{ev} (i)}$) is calculated by integrating the product of the flux $\Phi_i$, the IBD cross section $\sigma(E_{\bar{\nu}})$ \cite{Angular_dist_Vogel}, and the number of targets (in this case free protons) $N_p$, over the energy interval:

\begin{equation}
\frac{\Delta N_{\textrm{ev} (i)}}{\Delta t}= N_{p} \displaystyle\int_{E_{min}}^{E_{max}} \Phi_i(E_{\bar{\nu}},t) \sigma (E_{\bar{\nu}}) \, dE_{\bar{\nu}} .
\label{eq:Neventosi}
\end{equation}

\begin{figure}[t]
\centering
\includegraphics[width=0.5\textwidth] {flux_and_Xsec200.png}
\caption{\small{Total antineutrino flux per reactor at day 200 (solid curve with error band). The error includes the sum of the relative uncertainties of each of the 4 main fissile isotopes in the reactor. The dashed curve shows the parametrization suggested in~\cite{Xsec_DBI_vogel} with the fission rates calculated by DRAGON for the LVNPP. The continuous line shows the IBD cross section as given by~\cite{Angular_dist_Vogel}}}
\label{fig:flujoXsec200}
\end{figure}

Depending on the characteristics of the detector, only a fraction of these interactions will be observed. For a simple estimate, let this fraction be a uniform efficiency factor $\epsilon$. For neutrinos coming from nuclear reactors, $E_{min}$ is the threshold of 1.8 MeV and $E_{max}$ is $\sim~$10~MeV. The number of detected events for each isotope is then approximated by:

\begin{equation}
N_{\textrm{ev}(i)} =\epsilon \times N_{p} \frac{\Delta t}{4 \pi R^2}\displaystyle\int_{E_{min}}^{E_{max}}  S_i(E_{\bar{\nu}}) f_i(t) \sigma (E_{\bar{\nu}}) \, dE_{\bar{\nu}} ,
\end{equation}

where $\Delta t$ is a small exposure time compared with the time scale in which fission rates $f_i (t)$ change appreciably. Calculation for longer times requires an integration over time.

Finally the total number of events is equal to the sum of the events for each isotope:

\begin{equation}
N_{\textrm{ev (total)}} = \displaystyle\sum_{i=1}^4 N_{\textrm{ev} (i)}
\end{equation}

These are shown in Fig. \ref{fig:eventostodos}, considering three different detector efficiencies (5\%, 20\%, 30\% and 100\%) and counting for two consecutive days.

The authors of~\cite{PANDA} estimate an antineutrino detection efficiency of 9.24\% and an antineutrino event rate of 147 events/day in a 1 ton detector with an uncertainty of the order of 30\%. This is consistent, within errors, with our expected rate of 280 events/day (stable after day 350), once scaling for reactor power, distance, and assuming the same efficiency. The authors measured a background of $\sim$365 events/day, operating a 360 kg detector with the reactor OFF for 21 days. Scaling to a 1 ton detector corresponds to $\sim$1013 events/day. Since our expected rate at LVNPP is 26 events/day at the location of 100 m from the reactor cores, a background measurement at the level of 0.5\% ($\pm$5 events/day) would be necessary for a 5$\sigma$ detection of the antineutrinos, comparing the ON/OFF event rates with a similar detector.

\begin{figure}[t]
\centering
\includegraphics[width=0.5\textwidth] {events.png}
\caption{\small{Number of events accumulated over 2 days of exposure along a complete cycle of 400 days at LVNPP with two reactors in 1 ton of plastic scintillator. Curves for detection efficiencies (lower to higher) of 5\%, 20\%, 30\%, and 100\% are shown}}
\label{fig:eventostodos}

\end{figure}

\section{\label{sec:Conclusiones}Conclusions}

We calculated the antineutrino flux produced by the reactors at the LVNPP in Mexico using the DRAGON simulation code in the energy range 1.8 MeV\textless E$_{\nu}$\textless 8 MeV. The simulation provided the time evolution of the fission rates and hence the change of the flux along the 400 day long fuel cycle, starting with an initial load with no plutonium. A total systematic uncertainty on the flux ranging from 3.6\% to 9.8\%, depending on the antineutrino energy, was calculated assuming a 5\% uncertainty on the reactor power, and the uncertainties reported for the antineutrino spectra of the dominant fissile isotopes (~\cite{Fallot},\cite{Mueller}).Our calculation agrees well with a frequently parametrization \cite{Xsec_DBI_vogel} when the fission rates output by the simulation of the LVNPP BWR reactors are used.

The simulation code required the knowledge of generic parameters of the BWR reactors, at LVNPP, available in the literature, and showed the fission rates to have a moderate dependence on variations of the coolant, moderator and fuel temperatures for a fixed thermal power.

A segmented plastic scintillator detector of the type considered in~\cite{PANDA} located at 100 m from the two reactors could detect the neutrinos emitted, provided a background measurement with the reactors OFF is performed at the 0.5\% level.

\section*{\label{sec:Agradecimientos}Acknowledgements}
The authors acknowledge the support of UNAM-PAPIIT, grants number IB100413, IN112213 and CONACYT through grants CB-2009/00131598 and 398495 (scholarship holder number: 570620).
We also especially thank Dr. Guy Marleau from \'Ecole Polytechnique de Montr\'eal and Dr. Christopher Jones from MIT for their valuable help and advice throughout the installation and implementation of the DRAGON code simulation.

redpajama_set_name: RedPajamaArXiv