dataesr/scientific-paragraphs-categorization huggingface dataset:
However, as buildings have a long lifetime in European cities, we could use information on existing buildings (for which date of construction was known) to check if GENIUS was able to simulate their construction. The evolution of the density of construction, in terms of floor area, was not available but that of the population was well known (with good spatial resolution) and was used as a proxy. The GENIUS model was able to reproduce the construction of 91% of the LCZ types adequately; the construction date of these LCZ was acceptable, with 66% of buildings built at the right time, i. e. correctly within the ranges  1962-1974, 1975-1989 or 1990  onwards. Given that there are uncertainties on the construction dates from the census data itself, we consider this a good result. The simplified urban boundary layer model following  Bueno et al.
Acknowledgments This work has received support from the  National Agency of Research  for the  VURCA project  (reference  ANR-08-VULN-013  and the  MUSCADE  project (reference  ANR-09-VILL-0003 ) and from the thematic advanced research  network on Aeronautics and Space  for the  ACCLIMAT  project ( RTRA STAE -ACCLIMAT ). The authors thank  Dr Gerald Mills  for his editorials advice.
Conclusion This paper investigated the time-dependent lane reservation problem for hazardous material transportation, in which the transportation risk varies with time throughout the day. A new multiobjective mixed integer programming model was first proposed for the considered problem. Then a cut-andsolve method based -constraint method was developed. For improving the cut-and-solve method, a specific property of the considered problem was explored. Computational results showed that our method outperforms the optimization software package CPLEX. For the considered problem, one of the future research directions is to study properties of the model and attempt to reduce the search space of solution. Exploiting efficient piercing cuts is another way to improve the efficiency of the cutand-solve method.
Acknowledgments This work was supported in part by the  National Natural Science Foundation of China  ( 71071129  and  71471145 ), the  Natural Science Foundation of Shaanxi Province, China  ( 2012JM-9001 ),  Humanities, Social Sciences and Management Innovation Foundation of Northwestern Polytechnical University  ( RW201301 ),  1000 Plan for Foreign Talent  ( WQ20123400070 ),  Foreign Experts High-End Projects  ( GDW20123400148 ), and the  Ministry of Education Fund for Doctoral Student Newcomer Awards of China.
Methodology Four different databases were used in this study. Namely, the IAEA International Reporting System database IRS, the US Licensee Events Reports database LER, the French (IRSN) database SAPIDE and German (GRS) database KomPass. The screening period runs for 20 years, from 1991 to 2011 for IRS and LER, and from 1990 to 2010 for French and German databases. After screening, 145 IRS reports and 75 LERs were found to be applicable, to which 129 French event reports and 61 German event reports were added. The total number of events considered is 409. To help identify generic recommendations, the events were classified into families and sub-families according to their safety significance. To evaluate the lessons learned the following approach was applied: (1) Data preparation: extraction of the relevant information from each database.
Piping The pipes under pressure in the RCS or connected to RCS are usually made of austenitic or austenitic & ferritic stainless steel. Most connections are welded. The pipes may be exposed to various degradation phenomena (diverse hazards, mechanical fatigue, thermal fatigue, stress corrosion, etc. ). Event screening in the databases showed a total of 116 events (33 related to cracks and 83 to leaks). Three main causes for failure were identified, namely, fatigue, corrosion and the presence of manufacturing defects. Human factor induced defects proved to have little impact -less than 10% of the cases could be attributed to operation errors. Fatigue was found being induced by several factors: excessive vibration, pressure shocks and the thermal regime of operating the pipe, as well as by combinations of these factors.
Reactor pressure vessel and pressuriser Screening the databases revealed a total of 66 events (7 related to cracks and 59 to leaks) involving the reactor pressure vessel (RPV) and the pressuriser. The main cause of failure identified was corrosion. The events dealing with corrosion pointed to various causes, like steam impingement, high oxygen concentration, or use of materials containing water-soluble chlorides (asbestos) as an insulation material. 9 of all the 66 events selected were found dealing with inadequate material selection (mainly alloy 600). For example, all of the six events involving RPV head penetrations recorded into the SAPIDE database were related to the vulnerability of Inconel 600 to stress corrosion cracking. Other events were caused by the following deficiencies: deviation from modern design recommendations, inadequacy of the detailed written procedures, improper process of manual electric arc welding, debris on the vessel flange and post weld heat treatment at the manufacturer's works.
Steam generator (SG) tubes Screening the databases resulted in 88 events (14 related to cracks and 74 to leaks) involving SGs. The main cause of the SG tube defects was corrosion. It was found that corrosion was induced mainly by improper material selection (mainly alloy 600), and just in few cases by design deficiencies. A second important contributor represents the manufacturing defects, mainly resulted as failures of the Quality Assurance (QA) programme implemented during the fabrication process. Some events showed that a circumferential through-wall cracking can occur with a rapid degradation kinetic. In French PWRs, the tubes material varies depending on the year of construction, so the following tubes are found, respectively: "Inconel 600 MA" (Mill Annealed) tubes, "Inconel 600 HT" (Heat-Treated) tubes, and "Inconel 690 HT" (Heat-Treated) tubes.
Reactor coolant pumps Screening the databases revealed 29 events (5 related to cracks and 24 to leaks) dealing with reactor coolant pumps. The events recorded into the IRS database were related to inadequate seal design (upper rotating seal ring degradation/failure was the failure mode), to inadequate inspection method, to foreign substance intrusion into reactor coolant during operation and/or maintenance, and to the fact that damages on the seal water injection line filters could lead to clogging downstream of the seal housing. 19 events were recorded into the French national database alone. By their classification, there were: • Events involving damage to dynamic seals and leakage into the nuclear island vent and drain system (or into the reactor containment), • Events involving external leakage from a static seal, • Events involving lack or loss of screws or bolts tension and generalised corrosion in screws and bolts contributing to maintaining the integrity of the second containment barrier (with said lack or loss of tension causing borated water leaks which in turn result in generalised corrosion), • Events involving inadvertent interruption of coolant flow in the thermal barrier, followed by subsequent damage, events involving damage to the backseat seal, followed by leakage into the nuclear island vent and drain system (or into the reactor containment), • One event involving external leakage from a temperature sensor and • One event involving incorrect installation of seal no.
Safety relief valves Screening the databases revealed 18 events (2 related to cracks and 16 to leaks) involving safety relief valves. The events in the IRS database were related to the safety relief valves installed on the pressuriser (6 events). The analysis of French national database was limited to the safety relief valves (protection and isolation) installed on the pressuriser of the French PWRs. The analysis only retained events characterised by a failure or leak affecting the relief valve tandems of the pressuriser (valve, control cabinet and connections). The result of screening the French national database shows 8 events involving safety relief valves, of which 4 events involved "Banjo" fitting and/or "Jet" seal failures. Screening the German national database identified three events involving safety relief valves, all of them occurred at BWRs.
Isolation and control valves There were found a total of 65 events (7 related to cracks and 58 to leaks) in the databases involving these types of valves. Screening IRS database revealed that 5 of the 12 events dealt with maintenance induced corrosion, while corrosion alone caused just 2 events. Regarding the US NRC database, it was found that 4 out of the 6 recorded events dealt with manufacturing defects, caused in half of the cases by design deficiencies. By far, the highest number of events is recorded in the SAPIDE database. The events observed concern internal (upstream-downstream) and external (packing) leaks that were collected into tank or systems. Of 14 events involving packing gland failure, six involved pressuriser spray valves. Screening the KomPass database revealed a total of 7 events involving valves.
Flanges The flange joints and mechanical connections are mainly found in small-diameter pipes (instrumentation, venting and drain) and in the auxiliary pipes connected to the RCS. The leaks in the flange joints often are characterised by a slow flow rate and by damage localised in the seal. The observations of leaks (boron deposits), are often followed by the replacement of the seal. Screening the databases revealed 24 events dealing with flanges (1 related to cracks and 23 to leaks). Diverse causes were identified. It was found that the "O" rings used by the manufacturers were slightly oversized, so could not be contained inside the groove and was swelling outward under pressure. Other causes for leak were the lack of QA during maintenance and staff training, the utilisation of materials sensitive to intergranular and transgranular stress corrosion cracking on the flange contact surfaces and deficiencies in the installation procedures.
Not all these mechanisms were found in the analysis of events due to the limited number of events in the databases. Corrosion is the main root cause of the events analysed. In France, many corrosion induced events are due to Inconel 600 (SG tubes and vessel head penetrations). If we do not take into account these events, which are numerous, corrosion is not the main degradation mechanism. In France, corrosion is often a consequence of an external leak (boric acid). Manufacturing defects are the second largest root cause. These events are nearly all related to welding faults, but also it could be founded cases in which the manufacturing defect was just the "apparent cause", while it's precursors were dealing with inappropriate QA measures at the manufacturer. Fatigue is also an important degradation mechanism for the analysed events.
Method Participants and Procedure 118 healthy right handed participants (M age = 21. 7 years, SD age = 2. 8, 61 males) participated in the electroencephalographic (EEG) task. Data from 10 participants were not analyzable due to computer errors during recording of the data. Only participants with at least 30 correct No-Go trials (N = 95, 87%) were included in the EEG analysis. Additionally, only participants with at least 14 errors in the Eriksen Flanker (N = 70, 65%) were included. These sample selection criteria, and sample inclusion rates are similar to that of Olvet and Hajcak  [1] , Pontifex et al. [11] , and Meyer et al. [22, 23]. Using an online questionnaire, participants were screened for previous brain surgeries, pregnancy, or history of psychiatric disorders (no participants had to be excluded due to these criteria).
ERP Measurement & Statistical Analysis EEG was recorded using a Biosemi Active-Two amplifier system (Amsterdam, the Netherlands) at 32 scalp sites (positioned following the 10-20 International System and two additional electrodes: FCz and CPz) with active Ag/AgCl electrodes mounted in an elastic cap. Six additional electrodes were attached to the left and right mastoids, the two outer canthi of both eyes (HEOG), and the infraorbital and supraorbital region of the right eye (VEOG). All signals were digitalized with a sample rate of 512 Hz and 24-bit A/D conversion, with a band pass of 0-134 Hz. The data were off-line referenced to compute mastoids. Off-line, EEG and EOG activities were filtered with a band pass of 0. 15-30 Hz (phase shift free Butterworth filters; 24 dB/octave slope). During offline processing, no more than four bad channels per participant were removed from the EEG signal, and new values per channel were calculated using topographic interpolation  [24].
Data were segmented in epochs of 1000 ms (2200-800 ms after stimulus presentation) and 700 ms (2100-600 ms after the response) for inhibitory control and error processing, respectively  [24, 25, 27]. The average of 200 ms before stimulus onset in the Go/No-Go task and 100 ms before the response in the Eriksen Flanker period served as a baseline which was subtracted from all subsequent time points  [25, 27]. Segments with incorrect responses (i. e. , false alarm for No-Go trials, incorrect Go response, or false alarms for Eriksen Flanker trials) were all excluded from the EEG analysis  [24, 25]. After ocular correction  [28] , epochs, including an EEG signal exceeding 6100 mV, were excluded from the average  [23]. All epochs were also visually inspected for other artifacts. Average ERP waves were calculated after baseline correction for artifact-free trials at each scalp site in each condition.
e. , 2, 4, 6, 8, 10, …, and the participants' average, across all trials), and paired t-tests were used to determine statistically significant differences. Signal-to-Noise ratios (SNRs) were estimated using a process available in Brain Vision Analyzer Version 2. 0 software (www. brainproducts. com). First, noise is estimated by summing the squares of the difference between each data point and the average EEG value; this sum is then divided by the number of data points minus one. Second, average total power is estimated by taking the average of the squared values of each data point. Average power of the signal then equals the average total power minus the average noise power  [1]. SNRs of the trial pair averages were assessed using paired t-tests. Additionally, we assessed internal consistency measuring the correlation between these smaller trial averages and the N2/P3 and ERN/Pe participants' average (i.
Over the past decade, though, the Open (re)Source system has enabled broad scale disclosure of this information. Created and maintained by the online collective 6Anony-mousB, Open (re)Source is an online database of corporate information anonymously leaked by employees. This paper presents an ethnographic analysis of the Open (re)Source community, revealing two types of contributors: first, a group that are concerned about privacy and lawfulness, but believe that environmental impact data needs to be transparent; and second, a group that is disgruntled about corporate structures, and post information as retaliation. C. Computing for all: A sustainable infrastructure in a time of need.
ACKNOWLEDGMENTS This material is based in part upon work supported by the  DFG  (project  EnviroSiSE , grant number  PE2044/1-1 ) and the  National Science Foundation  under Grant No. 0644415. We would like to thank  Joseph Tainter  and  Lorenz Hilty  for valuable feedback and discussions as well as Reviewer 2 for helpful comments that made the rooting of the paper more explicit.
That was 2 years after the first concrete ideas for it had emerged, but still more than 1 year to go before the first "stable release" of Isabelle/jEdit with Isabelle2011-1 (October 2011). • In 2012 that initial release of Isabelle/jEdit was presented as system description and tool demonstration at CICM  [9]  and some of its concepts were explained at the co-located UITP 2012  [11]. • The subsequent releases of Isabelle/jEdit in May 2012, February 2013, and November/December 2013 have consolidated the PIDE concepts and its implementation. So many new things were introduced each time, that users have occasionally complained about having to re-learn the Prover IDE with each Isabelle release. The current official release Isabelle2014 (August 2014) is available from http://isabelle. in. tum. de/website-Isabelle2014 for Linux, Windows, Mac OS X.
The completion popup changes the keyboard focus to a different component, which can lead to odd effects of loosing key events in a situation where the user is typing fast, but the graphics display is too slow to catch-up (e. g. due to bad X11 rendering performance, which can happen both for local and remote displays). The lesson learned here is that a Prover IDE is a highly interactive computer-game, with demands of real-time reactivity that were not present in TTY front-ends from the past. Both the GUI event handling and the semantic aspects of completion in Isabelle/jEdit have been significantly reworked for Isabelle2014, according to the following general principles. • Syntactic completion is based on information that is immediately available in the editor, e. g. keyword tables for certain sub-languages of Isabelle, like the so-called "outer syntax" of Isabelle/Isar, or Isabelle/ML.
Completion for Isabelle symbols is an important a special case of this: when the user types "==>" he normally expects to get "=⇒" within formal text. • Semantic completion is produced by the prover eventually, after a full round-trip through the asynchronous PIDE protocol. This information usually arrives with a delay of 100-500 ms and is then merged with the available syntactic completion, before it is used for GUI rendering (e. g. for emphasis of text or a popup). • Completion markup may be produced by the prover in any of the following forms: -Language context guides the syntactic completion. Isabelle is a framework of many sublanguages, which have different requirements for completion. The language context for some text range informs the editor about the language name (e. g. to use a different keyword table), and some common flags like use of Isabelle symbols and antiquotations.
g. to determine ranges of prose text inside document sources or comments, the editor uses a conventional dictionary-based spell-checker to propose alternatives to words spotted in the text. This is important to write books and papers based on Isabelle theory sources, which is in fact the most relevant practical application of Isabelle over 15 years. Figure  3  illustrates spell-checking within informal text: the default dictionary does not know about Hilbert's, but this is not an error, merely highlighting. Moreover there is semantic completion within the term language, using an extra underscore to let the prover expose constants from the theory context. PIDE document content consists of sources that are augmented by semantic markup from the prover, as explained in  [7]. The abstract syntax for the markup follows untyped XML, and the semantics is often close to hypertext, with occurrences of formal entities in defining or referencing positions.
Hyperlinks are an important special case of that: prover markup is turned directly into familiar clickable spots in the text (via mouse hovering with the CONTROL or COMMAND modifier key pressed). In 2014 the visual appearance approximates that of major Web browsers further, e. g. due to change of the mouse pointer. There is now also the long-missing connection to an existing Navigator plugin from the jEdit repository, which is a rare case of successful re-use of software components: no special tricks nor reconsideration of the underlying concepts were required, to make Isabelle/jEdit converge with regular HTML browsers in this respect. Isabelle/jEdit text areas with markup and hyperlinks are used uniformly wherever that makes sense: for the main editor buffer, output panels, tooltips etc. The user who sees a printed term somewhere can follow the implicit links to the definitions of the formal entities shown there, and return easily to the.
The Prover IDE takes care to forward the correct version of auxiliary file content to the prover as a blob, but without using the global file-system. 2 his extra file management is particularly relevant for development of Isabelle/HOL itself within the Prover IDE. According to usual practice of LCF-style proof assistants, the main logical environment emerges by alternating theory specifications with ML modules. It is now possible to use Isabelle/jEdit to explore the inner workings of Isabelle/HOL modules and their dependencies on theory content, notably in conjunction with the navigation support explained above ( §4). For live editing of the Isabelle/HOL sources, the logic session image of Isabelle/jEdit needs to be set to Pure, which requires a restart of the Prover IDE. Then any of the theories may be opened, e.
g. $ISABELLE_HOME/src/HOL/HOL. thy by using that path notation literally in the jEdit file browser (even on MS Windows). The ML file commands in such theories refer to Isabelle/ML modules that are compiled on the spot. By default the prover reads the source from the file-system, but by following the implicit hyperlink of the file argument (or opening files in the jEdit file-browser) the editor takes over the responsibility for the sources and its subsequent changes. Thus the user may edit Isabelle/ML source files, without ever saving the content, while the Poly/ML compiler provides continuous feedback on warnings, errors, name references, inferred types etc. as part of the PIDE document model (see figure  5 ). This works reasonably well for source files up to 100 KB each. The total volume of ML sources contributing to Isabelle/HOL is actually so high that its cumulative PIDE markup requires more than 2 GB Java heap space.
Thus Isabelle/jEdit can be used as IDE for SML'97, without any connection to theory or proof development. The two ML environments are managed independently within the same runtime system, but there are also simple means to exchange toplevel ML bindings, e. g. to re-use the parallel functional programming library of Isabelle/ML in Standard ML, or to print messages in Standard ML that are recognized by the Prover IDE for its Output panel. The Prover IDE provides some simple examples for that in its Documentation panel, in the entry for $ISABELLE_HOME/src/Tools/SML/Examples. thy that is only a single click away from direct editing and browsing. Here the enclosing theory is used like a project file for SML modules, with the possibility to add extra explanations around it. Thus Standard ML has gained a reasonably modern IDE after some decades of waiting.
Navigation of the sources works as usual ( §4), but semantic completion ( §3) is still missing because Poly/ML (version 5. 5. 2) does not provide that information. Also lacking is support for the interactive debugger of Poly/ML. Such further fine-grained interaction with the ongoing execution process would be quite useful for other Isabelle languages as well, e. g. to analyse the behaviour of tactical expressions beyond the single-stepping of outermost commands or adhoc printing of intermediate states. If that train of thought is continued further, it could meet with recent trends towards "live programming", as advocated by Bret Victor on his blog 3  , for example. This is a revival and continuation of older ideas from Smalltalk of the 1970s and 1980s, but adapted to the possibilities of the hardware from today.