dataesr/scientific-paragraphs-categorization huggingface dataset:
Introduction The Fourth Workshop on Sustainable Software for Science: Practice and Experiences (WSSSPE4) 1 was held over 2 1/2 days on 12-14 September 2016 in Manchester, England, with 68 attendees. This location and date was selected so that WSSSPE4 immediately preceded the First Research Software Engineers (RSE) Conference. Previous WSSSPE events, 2 all of which were in the US, were two general, presentation-focused, one-day workshops held with the SC13 and SC14 conferences  [1] [2] [3] [4] , two half-day workshops 3 held with SciPy 2014 and 2015 that contained presentations about specific sustainable Python software packages, and a 1-and-1/2-day workshop that included teams that self-assembled and discussed focused software sustainability topics  [5]. Based on the work done at these previous WSSSPE meetings, WSSSPE4 was aimed at producing working groups that would better continue working after the workshop ended.
These funds allowed 29 additional attendees (of 44 applicants), including 11 students and five early-career researchers. WSSSPE4 also included two professional event organizers/facilitators who helped plan the workshop agenda, and who engaged with participants during the workshop. This paper is a summary of a longer report  [6]  on the workshop and the submitted materials. The remainder of the paper includes the call for papers ( §2); the WSSSPE Code of Conduct ( §3) and mission and vision ( §4); a set of presentations that included a keynote, papers, lighting talks, and a panel ( §5); and the activities of a set of working groups ( §6). One full day of the workshop was spent with participants in the working groups, which occurred in parallel with each other. And each of the working groups left with a plan for how they could move forward.
Call for participation Post-WSSSPE3 feedback said that attendees had two distinct motivations for attending: to make a better future for research software, and to immediately do better research software development. Thus, WSSSPE4 was planned as two tracks: The call for participation requested: idea papers, implementable proposals related to Track 1; position papers, longer, not previously published papers discussing what we can do to improve sustainable scientific software in the short term; experience papers, longer papers that discuss current experiences and how they have been used to improve the quality of today's research software and/ or the experiences of its developers; demos, brief papers describing a tool or process that would be demonstrated that improves the quality of today's research software and/or the experiences of its developers; and extended abstracts describing lightning talks, where each author could make a brief statement about work that either had been done or was needed.
Code of Conduct WSSSPE4 introduced a Code of Conduct (CoC), 4 which was conceived for the workshop and as guidance for the community of scientists that WSSSPE supports, including their personal and online interactions (e. g. , on Twitter, in email lists, in Slack). This CoC is based on the FORCE11 conference CoC  [8] , which is in turn based on the Code4 Lib CoC  [9]. In introducing the CoC, we asked participants to agree to the following main guidelines: WSSSPE events are community events intended for networking and collaboration as well as learning. We value the participation of every member of the community and want all attendees to have an enjoyable and fulfilling experience. Accordingly, all attendees are expected to show respect and courtesy to other attendees throughout the event and in interactions online associated with the event.
The WSSSPE event organizers are dedicated to providing a harassment-free experience for everyone, regardless of gender, gender identity and expression, age, sexual orientation, disability, physical appearance, body size, race, ethnicity, religion (or lack thereof), technology choices, or other group status. To make clear what is expected, everyone taking part in WSSSPE events and discussions-speakers, helpers, organizers, and participants-is required to conform to the Code of Conduct. The CoC was discussed at the beginning of WSSSPE4, with the CoC subcommittee and a general email address for reporting concerns or incidents, or asking questions. One concern was raised after the first half day, and we changed the workshop to address this concern.
Presentations The keynote was given by Patricia Lago and entitled "The legacy of unsustainable software". Sustainability is broadly associated with natural ecologic systems. When we translate the notion of sustainability to software solutions, however, we often confuse impact in a certain point in time with balanced and durable effects. In addition, software sustainability adds a fourth dimension to environmental, social and economic aspects: technical sustainability, and hence higher complexity  [10]. Lago's keynote discussed the challenges (and some related ongoing research) of combining technical and environmental sustainability, providing a complementary angle to the workshop discussions. WSSSPE4 included the presentation of 12 10-minute talks (based on four idea papers, three position papers, two experience papers, and three demos) that addressed a wide range of topics around sustainability for software in science.
" These were: Alice Allen, Editor, Astrophysics Source Code Library, who brought an understanding of the difficulties of organizing a community and curating their software; Mike Croucher from the University of Sheffield and Rob Haines from the University of Manchester who are both Research Software Engineers with decades of experience of writing code for researchers; Patricia Lago from Vrije Universiteit Amsterdam, who brought a fresh perspective on software sustainability from the point of view of its impact on society and business; and Karthik Ram from the Berkeley Institute for Data Science, who brought his perspective on the practicalities of using scientific software to conduct his research as a data scientist.
Verifying best practices and metrics for sustainable research software Many open source research software projects document their best practices that contribute to the sustainability of the software as well as the metrics that define their research software project's success. This group will take the outputs of the WSSSPE efforts to identify best development practices and to identify metrics for sustainable research software, and cross-reference them with current open source research software that successfully uses modern software engineering. This will allow the group to identify gaps on both sides and to hypothesize how successful projects can be further improved. One can join this group or obtain more information about it by sending an email to the verifying best practices & metrics for sustainable research software group: <wssspe4-verify-best-practices@ googlegroups.
Software Sustainability Alliance The Software Sustainability Alliance working group aims to establish an alliance between organizations interested in improving the sustainability of research software at a larger scale than their local university or community, and to distinguish between this group and WSSSPE. Such an alliance would ease the collaboration between member organizations to improve the sharing of expertise, resources and best practices. It is currently seeking feedback on potential activities and member organizations, as well as the aims and scope of this alliance. Currently, pointto-point collaboration exists between organizations, but this inadvertently results in competition or redundancy within the sustainable software community. An alliance of software sustainability organizations would ease inter-organization collaboration and the promotion of software sustainability, andwould improve the pooling of competencies and the sharing of expertise.
The group's objective is development of a prototype tool that allows domain scientists to generate simulation prototypes through a simple, yet expressive declarative stronglytyped programming language close to equational expressions. The result of that specification is both an executable artifact as well as a specification for scientific programmers to later flesh out completely and adapt to particular infrastructures. To join this project, one can visit the GitHub repository (https://github. com/nunezco2/ S2PI) or join #wg-sci-soft-proto in the WSSSPE Slack.
CodeMeta Research software is often not shared; that which is shared may not have much metadata associated with it, and that which does exist often does not travel further than the website on which the software resides. The CodeMeta project 6 wants to incentivize software developers to release their software, encourage the development of metadata for it, enable credit assignment and citation of research software, increase its discoverability, more easily track dependencies, and enable reuse of software metadata, all goals that WSSSPE attendees have great interest in supporting. CodeMeta seeks in part to create a "Rosetta Stone" for software metadata to facilitate retaining such metadata between repositories, services, registries, indexers, publishers, citation managers, and other entities that create, ingest, use, and/or store metadata about software.
The project also wants to establish a JSON-LD schema as a tool for making metadata machine-readable  [45]. While at WSSSPE4, the group greatly expanded the CodeMeta project README file to include a description of the project geared to those with little or no prior knowledge of the project, a list of contributors, information on how one can get involved, a brief project history and who is managing the project, and links to additional information. Though a Google group mailing list has been established for the working group, the easiest way to engage with the CodeMeta project is through its Github repository: https://github. com/codemeta/codemeta.
Ideally these people will be brought together for a short workshop or hackathon with the goal of drafting the curriculum. Anyone interested in contributing can join the Google Group/mailing list (https://groups. google. com/forum/#!forum/wssspe4software-best-practices-for-undergraduates), join the #wg-undergraduatecourse channel in the WSSSPEs Slack, or ask to join the WSSSPE4-undergraduatecourse organization (https://github. com/orgs/ WSSSPE4-undergraduate-course).
Coordinating access to continuous integration (CI) for research software Each developer of software with uncommon needs (hardware, software, libraries, data sets), non-public code, or tests that exceed time limits for free plans must acquire, setup, and maintain their own continuous integration systems because their needs make them ineligible for popular free services such as Travis CI. For example, software groups that develop BIOUNO, CI4SI, or GROMACS have done this. This group is interested in reducing the burden of different projects having to build and maintain their own continuous integration systems (when publicly available CI are not a fit), by coordinating and sharing this burden across multiple projects. However, there are a lot of open issues such as how can the group learn from existing similar work without reinventing the wheel.
This working group will (1) conduct a literature survey to gauge the extent of awareness of the issue in general, (2) generate content useful for the community where needed, and (3) curate the collected and added content for the use of the community. To join this effort, one can use the #wg-testing-in-science channel in the WSSSPE Slack. Additionally, a git repository (https://github. com/ WSSSPE/WG-Best-Practices. git) exists for contributing content and reference to, and curation of the existing literature on this topic.
Open research index The aim of this group is to investigate the building of an index of research products in an open sustainable manner. Its goal is not to eliminate commercial products, but to build on what is there and provide data and services that are missing. The Open Research Index would take in all research products (papers, software, datasets, workflows, etc. ) from their publishers and recorders (journals, societies, domain repositories, government [open access] repositories, preprint servers, general repositories [e. g. , figshare, zenodo]) and other services (CrossRef, ORCID). Each product would list authors and citations and allow people to search the resulting network. Users would also be able to interact with their own record and edit it, as Google Scholar allows. The group's plans are relatively simple to express, though quite complex to undertake; the first is to identify a leader.
The survey results indicate that future WSSSPE conferences should consider the balance of the attendees. WSSSPE4 had many first time and early career participants who would have benefited from a review of basic concepts and terminology including what it means for software to be sustainable and the roles of research software engineers. Additional emphasis and topics to explore would be the inclusion of more case studies, focus on the decision making process in developing and using software, deeper dives into selected topics, tutorials, software training within and outside of STEM, lowering the barriers to implementing best practices in software development, and progress towards executing WSSSPE's vision.
Without a process to resolve this concern, the utility of further multi-day WSSSPE workshops is unclear, at least to start new activities. On a more positive note, WSSSPE4 was successful as a gathering place to discuss scientific software sustainability, and for groups that are already in place or that can be composed of related funded activities to meet. Future WSSSPE meetings will likely combine these functions: a meeting place for like-minded individuals, a place to share experiences and lessons learned, and a place for both existing groups and sets of related projects to meet in person. Other parts of the WSSSPE infrastructure (the email list and the Slack) will be used both for general discussions, as well as for groups that choose to focus on specific problems. After WSSSPE4, we also have learned enough to summarize the areas of active work in sustainable scientific software, based on the WSSSPE4 mission and vision statements, the WSSSPE4 call for participation (based on topics in previous WSSSPE meetings), and the working groups formed in WSSSPE4.
The paper documents the implementation and validation of the coupled simulation of the propulsion system and vehicle performed during the 4th development phase of the ESPSS (European Space Propulsion System Simulation) library running on the existing platform EcosimPro. This covers a signi¦cant update of the spacecraft propulsion system modeling: the Fluid §ow, Tanks and Combustion chamber components are updated to allow coupling to the vehicle£s motion, the Archimedes pressure coming from acceleration and rotations given by the vehicle or by any perturbation forces are taken into account, several new features are added to the Satellite library along with new components enabling full attitude control of a platform. A new powerful compact equation is presented for solving elegantly the Archimedes pressure coming from combined acceleration and rotation in the most general case (noncollinear).
INTRODUCTION In the frame of the 4th development phase of the ESPSS library [13] running on the EcosimPro platform  [4] , the implementation and validation of the ¤coupled simulation of the propulsion system and vehicle¥ is discussed. EcosimPro is a object-oriented Physical Simulation Modeling tool dedicated for system analyses. Its visual simulation interface is capable of solving various kinds of dynamic systems represented by writing equations and discrete events. It can be used to study both transients and steady states. For example, with the propulsion libraries ESPSS from European Space Agency (ESA), the user draws (and designs at the same time) the propulsion system with components of that speci¦c library consisting of tanks, lines, ori¦ces, thrusters, tees, etc. The user can enhance the design with components from the thermal library (heaters, thermal conductance, and radiators), the control library (analogue/digital devices), the electrical library, etc.
ESPSS BACKGROUND EcosimPro is a Physical Simulation Modeling tool developed for ESA by Empresarios Agrupados Internacional (Spain) since 1989. EcosimPro was a precursor and now, with its 28 years of careful growing, it belongs to the last generation of the common engineering tools after computer aided design (CAD) and integrated engineering analysis tools available on classical laptops. The kernel of EcosimPro is an expert solver of all the equations set in the di¨erent components of a system. Thanks to such expert solver, the tool allows to manipulate components like objects that can be independently further developed with more sophisticated equations. EcosimPro is based on a visual simulation tool for solving simple and complex physical processes that can be expressed in terms of equations (including ordinary di¨erential equations and di¨erential-algebraic equations) and discrete events.
Practically, the modeling of physical components is based on a basic ¤Ecosim-Pro language¥ (EL), an object-oriented programming language which is very similar to other conventional programming languages (Basic, C++) but is very powerful to write any equations and di¨erential equations for modeling continuous and discrete processes. EcosimPro employs a set of libraries containing various types of components (mechanical, electrical, pneumatic, hydraulic, etc. ) which can be interconnected to model complex multidomain dynamic systems. The ESA ESPSS is a set of EcosimPro libraries written to model all aspects of a functional propulsion system. As a tool, ESPSS is relying on onedimensional (1D) §ow equations, thermodynamic relationships, and real §uid properties, there is no need for fudge factors; therefore, the results of the simulation could be considered as general as long as the §ow is 1D and homogeneous (either as monophase, or two-phase state or as a mixture).
CONCLUDING REMARKS The paper has presented in detail the progress made during the 4th phase of the work performed on the ESPSS library within the existing tool EcosimPro. The signi¦cant advance is related to the implementation of the Archimedes pressure for the most general case of noncollinear acceleration and angular rate for the ESPSS §uid components. Thanks to the use of a new very compact equation, this could be performed in a much easier form than in the previous complex formulations. This has been successfully implemented for the components needed for a propulsion system. Two examples of propulsion systems have been presented with highlights the coupling between propulsion vehicle. Among the progress, new components have been implemented successfully into the Satellite library allowing to simulate with ¤good¥ realism typical spacecraft missions, particularly of interest for propulsion applications as the attitude control for a small satellite with thrusters.
In the framework of the French National Research Agency program on nuclear safety and radioprotection, the 'DIstributed Sensing for COrium Monitoring and Safety' project aims at developing innovative instrumentation for corium monitoring in case of severe accident in a Pressurized Water nuclear Reactor. Among others, a new under-vessel instrumentation based on Self-Powered Neutron Detectors is developed using a numerical simulation toolbox, named 'MATiSSe'. The CEA Instrumentation Sensors and Dosimetry Lab developed MATiSSe since 2010 for Self-Powered Neutron Detectors material selection and geometry design, as well as for their respective partial neutron and gamma sensitivity calculations. MATiSSe is based on a comprehensive model of neutron and gamma interactions which take place in Selfpowered neutron detector components using the MCNP6 Monte Carlo code.
The LDCI's SPND simulation toolbox, named 'MATiSSe', standing for 'Monte cArlo Tool for SPND Simulation', is used to select SPND materials, to design geometries and to ensure that such detectors remain operational in any reactor situations. Full expected partial neutron and gamma sensitivities are calculated using the MATiSSe toolbox. The THERMOCOAX SAS Company is currently manufacturing prototypes to be tested in 2017 in a European research reactor.
C. The LDCI MATiSSe Toolbox The LDCI MATiSSe toolbox was developed to ease operator calculations for self-powered neutron detector design, simulation and operation. It runs the multistep SPND model in adequate order from a user SPND definition (see figure  6 ). The reaction contributions are evaluated through multistep Monte Carlo calculations using the MCNP6. 1 code and the JEFF3. 2 neutron data and the ENDF/B-VII. 1 gamma data libraries. The JANIS4. 0 web nuclear data application  [13]  provides the β -energy spectra. In the MATiSSe toolbox, each Monte Carlo and analytical calculation are coded separately in C++ macros. The user defines both the SPND geometry and its close environment, and then launches calculations from a graphical user interface (GUI) developed with the Qt Creator 3. 5.
0 program (ICS Company). Two different modes are available: 'automatic' one is running all steps automatically up to the final output current, and 'expert' mode is a step-by-step mode for advanced users. At the end, the MATiSSe output is a direct electrical current comparable to the current generated in the SPND when irradiated in the same neutron and gamma conditions. Experiments dedicated to MATiSSe toolbox qualification have been performed successively in the French CEA Saclay OSIRIS reactor, in the Slovenian TRIGA Mark II reactor (Jozef Stefan Institute -JSI) and in the Polish MARIA reactor (National Centre for Nuclear Research -NCBJ)  [14, 15]. Various SPNDs (standards and innovative ones) have been tested in systematically and fully characterized locations and confronted to MATiSSe toolbox simulations.
VI. CONCLUSION In the framework of the ANR DISCOMS project, the feasibility of a remote corium migration monitoring in the unlikely event of a severe nuclear accident is considered and simulated. The corium progression is monitored by means of an instrumented pole equipped with SPNDs and a Thermocouple. CEA laboratories and the THERMOCOAX SAS Company have designed an instrumented pole according to the considered implementation and irradiation conditions. These conditions for GEN2 reactors have been estimated by DISCOMS partners (IRSN and CEA/SERMA). A Rhodium and a Platinum emitter SPNDs are encapsulated in this instrumented pole. Their performances have been calculated using the LDCI numerical tool called 'MATiSSe' for different SPND locations. MATiSSe toolbox simulation results provide SPND currents that demonstrate the proposed instrumented pole capabilities.
government launched an important research program on nuclear safety and radioprotection (RSNR), managed by the  French National Research Agency (ANR). This strategic initiative is co-funded by the government and run by the  General Commissariat of Investment (CGI)  through the  'Investments for the Future' Program (PIA). In this context, the  DISCOMS  project , which stands for 'DIstributed Sensing for COrium Monitoring and Safety ', Manuscript received April 19 th , 2017. This work was supported by the RSNR research program on nuclear safety and radioprotection managed by the  French National Research Agency (ANR). L.