- Allocations-admins - mailman3.cels.anl.gov

[LCRC Accounts] Project Allocation Request
by accounts＠lcrc.anl.gov 10 Jun '17

10 Jun '17

Hello, A change in allocation has been requested: Requester: sinclair (Donald Sinclair) Project: Lattice-QCD Title: Lattice simulations of QCD at finite baryon number density Description: A field theory in the Euclidean time regime can be quantized in terms of a partition function which is the functional integral over the c-number fields of the exponential of minus the action. In the Langevin equation, the fields evolve in a fictitious time such that the derivative of each field with respect to this time is minus the derivative of the action with respect to that field -- the drift term -- plus a gaussian distributed random number appropriately normalized. It can be shown that in the large 'time' limit the fields are distributed with weight exp(-S), where S is the action. The Langevin equation can be extended to the case where S is complex, by replacing the real fields by complex fields. Here it can only be demonstrated that the time averages of observables give the correct expectation values, when the region traversed by the fields is compact and S is holomorphic in the fields. When this Complex Langevin Equation (CLE) is applied to Lattice QCD, the gauge fields must be extended from SU(3) to SL(3,C) and the action involves the gauge fields and their inverses, but not their hermitian conjugates. The fermions are integrated out producing a power of the determinant of the Dirac operator. We obtain an effective action for the gauge fields by using the identity, determinant(M)^q=exp{q*ln[determinant(M)]} =exp{q*Trace[ln(M)]}. The trace is replaced by a stochastic estimator. The derivative with respect to the fields introduces an inverse of the Dirac operator M, which is evaluated using the conjugate gradient method. Unfortunately, since the determinant has zeros, the inverse of M and thus the drift term have poles, so that the drift term is not holomorphic but meromorphic in the fields. It is for this reason that, although the domain over which the fields evolve appears compact, convergence of the observables to their correct values is not guaranteed, and must be checked. We integrate the CLE numerically, inverting the Dirac operator using the conjugate gradient method. The fermion fields are placed on the sites of a 4-dimensional hypercubic lattice and the gauge fields on the links, making the action gauge invariant. If we label the sites by the 4-vector (x,y,z,t), we parallelize using MPI giving each task 1 t coordinate and nz adjacent z coordinates. The x and y coordinates are internal to each task. Each task then performs the same number of operations, and the communications are all nearest neighbour and homogeneous. In particular M only connects nearest-neighbour sites and is sparse. M is discretized using the staggered fermion method. Gauge cooling is implemented to minimize the sum over links of Tr{UU^dagger+(UU^dagger)^[-1]-2}, where U are the lattice gauge fields. Because we use 64-bit floating point (our previous simulations used 32-bit floating point except places where precision is critical), scaling is not as good as is in our previous work. In addition, since we can anticipate algorithmic changes, we have not optimized our conjugate gradient routine as aggressively as before. We plan to do this, as soon as we are satisfied that we have an optimum version. We only have absolute (Gflop) performances for 12^4 lattices measured on NERSC computers. The best such performance was 3.0 Gflops/core on Cori. We assume that the best performances on NERSC machines for 16^4 lattices would be similar. On 64 cores the performance of the code on a 16^4 lattice on the 32 core Haswell nodes of Blues was approximately 10% slower than on Cori. On the 16 core Blues nodes, the performance was approximately 25% slower than on Cori. For scaling studies on Blues, see the Large Allocation Efficiency section. We have performed runs on a 12^4 lattice at beta=6/g^2=5.6 (g is the lattice QCD bare coupling) and quark mass m=0.025, over a wide range of mu values. The results of these runs are in qualitative agreement with what is expected. However, there are quantitative deviations from our expectations. Running with the same beta and m values on a 16^4 lattice for a selection of mu values showed that these deviations are not a finite volume effect. On the 16^4 lattice we are able to simulate at weaker coupling (beta=5.7). At mu=0 we find far better agreement with known results than for beta=5.6. We are extending our beta=5.7 simulations to mu =/= 0 on Blues and Bridges at PSC to determine if there is similar improvement away from mu=0, and propose to continue these runs in FY2017. Note that we have less than 500,000 hours on Bridges until January, 2017. The current runs being performed on Blues are on 16^4 lattices, where we are using 64 cores (2 32-core Haswell nodes). Each job takes 50-60 wallclock-hours. We plan to run similar jobs in FY2017. We intend to run 2 such jobs concurrently, or 1 128 core job. When we are convinced that we have the code we wish to run in extensive production, we will apply optimizations that have proved effective with other codes, to the conjugate gradient routine where the jobs spend most of their time. Project website:www.hep.anl.gov/dks Current: undetermined amount Justification: We estimate that our code achieves approximately 3 Gflops per core on the Haswell nodes for the 64 cores we plan to use for production. 64 cores is the 'sweet spot' for 16^4 lattices where the per core performance is maximum. The following table shows wallclock times for identical benchmark runs on various numbers of cores on the 32-core Haswell nodes on Blues. Each run used all 32 cores on each node, and 1 task/core. 32 cores haswell = 51m44.125s 64 cores haswell = 21m41.861s 128 cores haswell = 13m3.596s 256 cores haswell = 9m43.317s The following table shows wallclock times for identical benchmark runs on various numbers of cores on the 16-core nodes on Blues. Each run used all 16 cores on each node, and 1 task/core. 16 cores = 129m35.228s 32 cores = 52m37.305s 64 cores = 25m35.144s 128 cores = 17m55.801s 256 cores = 16m40.058s As indicated above these numbers would be expected to improve when we apply further optimizations to the conjugate gradient code, which have proved effective on other, similar codes. Our request is based on performing 2 64-core or 1 128-core job continuously, assuming that Blues will be available for production 90% of the time. Requested: 100000 A specific reason has been given: Needed to complete present runs This needs to be approved and the final allocation amount decided upon. Thank You, The LCRC Accounts System

1 0

[LCRC Accounts] Project Allocation Request
by accounts＠lcrc.anl.gov 10 Jun '17

10 Jun '17

Hello, A change in allocation has been requested: Requester: sinclair (Donald Sinclair) Project: Lattice-QCD Title: Lattice simulations of QCD at finite baryon number density Description: A field theory in the Euclidean time regime can be quantized in terms of a partition function which is the functional integral over the c-number fields of the exponential of minus the action. In the Langevin equation, the fields evolve in a fictitious time such that the derivative of each field with respect to this time is minus the derivative of the action with respect to that field -- the drift term -- plus a gaussian distributed random number appropriately normalized. It can be shown that in the large 'time' limit the fields are distributed with weight exp(-S), where S is the action. The Langevin equation can be extended to the case where S is complex, by replacing the real fields by complex fields. Here it can only be demonstrated that the time averages of observables give the correct expectation values, when the region traversed by the fields is compact and S is holomorphic in the fields. When this Complex Langevin Equation (CLE) is applied to Lattice QCD, the gauge fields must be extended from SU(3) to SL(3,C) and the action involves the gauge fields and their inverses, but not their hermitian conjugates. The fermions are integrated out producing a power of the determinant of the Dirac operator. We obtain an effective action for the gauge fields by using the identity, determinant(M)^q=exp{q*ln[determinant(M)]} =exp{q*Trace[ln(M)]}. The trace is replaced by a stochastic estimator. The derivative with respect to the fields introduces an inverse of the Dirac operator M, which is evaluated using the conjugate gradient method. Unfortunately, since the determinant has zeros, the inverse of M and thus the drift term have poles, so that the drift term is not holomorphic but meromorphic in the fields. It is for this reason that, although the domain over which the fields evolve appears compact, convergence of the observables to their correct values is not guaranteed, and must be checked. We integrate the CLE numerically, inverting the Dirac operator using the conjugate gradient method. The fermion fields are placed on the sites of a 4-dimensional hypercubic lattice and the gauge fields on the links, making the action gauge invariant. If we label the sites by the 4-vector (x,y,z,t), we parallelize using MPI giving each task 1 t coordinate and nz adjacent z coordinates. The x and y coordinates are internal to each task. Each task then performs the same number of operations, and the communications are all nearest neighbour and homogeneous. In particular M only connects nearest-neighbour sites and is sparse. M is discretized using the staggered fermion method. Gauge cooling is implemented to minimize the sum over links of Tr{UU^dagger+(UU^dagger)^[-1]-2}, where U are the lattice gauge fields. Because we use 64-bit floating point (our previous simulations used 32-bit floating point except places where precision is critical), scaling is not as good as is in our previous work. In addition, since we can anticipate algorithmic changes, we have not optimized our conjugate gradient routine as aggressively as before. We plan to do this, as soon as we are satisfied that we have an optimum version. We only have absolute (Gflop) performances for 12^4 lattices measured on NERSC computers. The best such performance was 3.0 Gflops/core on Cori. We assume that the best performances on NERSC machines for 16^4 lattices would be similar. On 64 cores the performance of the code on a 16^4 lattice on the 32 core Haswell nodes of Blues was approximately 10% slower than on Cori. On the 16 core Blues nodes, the performance was approximately 25% slower than on Cori. For scaling studies on Blues, see the Large Allocation Efficiency section. We have performed runs on a 12^4 lattice at beta=6/g^2=5.6 (g is the lattice QCD bare coupling) and quark mass m=0.025, over a wide range of mu values. The results of these runs are in qualitative agreement with what is expected. However, there are quantitative deviations from our expectations. Running with the same beta and m values on a 16^4 lattice for a selection of mu values showed that these deviations are not a finite volume effect. On the 16^4 lattice we are able to simulate at weaker coupling (beta=5.7). At mu=0 we find far better agreement with known results than for beta=5.6. We are extending our beta=5.7 simulations to mu =/= 0 on Blues and Bridges at PSC to determine if there is similar improvement away from mu=0, and propose to continue these runs in FY2017. Note that we have less than 500,000 hours on Bridges until January, 2017. The current runs being performed on Blues are on 16^4 lattices, where we are using 64 cores (2 32-core Haswell nodes). Each job takes 50-60 wallclock-hours. We plan to run similar jobs in FY2017. We intend to run 2 such jobs concurrently, or 1 128 core job. When we are convinced that we have the code we wish to run in extensive production, we will apply optimizations that have proved effective with other codes, to the conjugate gradient routine where the jobs spend most of their time. Project website:www.hep.anl.gov/dks Current: undetermined amount Justification: We estimate that our code achieves approximately 3 Gflops per core on the Haswell nodes for the 64 cores we plan to use for production. 64 cores is the 'sweet spot' for 16^4 lattices where the per core performance is maximum. The following table shows wallclock times for identical benchmark runs on various numbers of cores on the 32-core Haswell nodes on Blues. Each run used all 32 cores on each node, and 1 task/core. 32 cores haswell = 51m44.125s 64 cores haswell = 21m41.861s 128 cores haswell = 13m3.596s 256 cores haswell = 9m43.317s The following table shows wallclock times for identical benchmark runs on various numbers of cores on the 16-core nodes on Blues. Each run used all 16 cores on each node, and 1 task/core. 16 cores = 129m35.228s 32 cores = 52m37.305s 64 cores = 25m35.144s 128 cores = 17m55.801s 256 cores = 16m40.058s As indicated above these numbers would be expected to improve when we apply further optimizations to the conjugate gradient code, which have proved effective on other, similar codes. Our request is based on performing 2 64-core or 1 128-core job continuously, assuming that Blues will be available for production 90% of the time. Requested: 100000 A specific reason has been given: Needed to complete present runs This needs to be approved and the final allocation amount decided upon. Thank You, The LCRC Accounts System

1 0

[LCRC Accounts] Project Allocation Request
by accounts＠lcrc.anl.gov 09 Jun '17

09 Jun '17

Hello, A change in allocation has been requested: Requester: leicheng (Lei Cheng) Project: ElectrolyteRedoxFlow Title: discoveries of electrolyte for redox flow batteries Description: In this renewal work, we will focus on stability studies of redox-active molecules for aqueous redox flow battery application. A short list of redox-active molecules for NRF application down-selected through high-throughput screening scheme were synthesized and tested experimentally (Moore and Brushett). The validation work shows that most of the compounds have irreversible redox activity, suggesting their instability in charged states. Similar phenomenon has been observed for molecules screened for aqueous redox flow (ARF) application. For example, catechol molecule can potentially be used as active catholyte materials in ARF battery. The electron-withdrawing group nitro is added to increase the oxidation potential of the catechol base molecule and it was predicted to increase the oxidation potential by 0.2 V. However, the experimental cyclic voltammetry measurements show that the oxidation of nitro-substituted catechol is not reversible (no reduction observed ) though the oxidation potentials agree well with calculation (courtesy of Zhang and Su, ANL). We are investigating addition reactions (1,2-addition and 1,4-addition) by H2O molecule as possible degradation reaction mechanism on a series of hydroquinone compounds with available experimental reversibility data. This study will shed light on possible stability predictors such as substitution site and electron-activating strength of substituent, as well as designing more stable molecules for this category of compounds. Current: undetermined amount Justification: All calculations will be performed using Gaussian. This package is considered very efficient and reliable for quantum chemistry calculations. Gaussian is not very scalable but it provides really robust geometry optimizer and the G3/G4 methods are built-in. The size of molecules we propose to study is very typical for the computational software (Gaussian) so they scale reasonably well for most DFT calculation. The higher level calculations will consume more memory as well as computational time. Requested: 350000 A specific reason has been given: I had to do some transition state search to look for decomposition pathways of some molecules using Gaussian and NEB within VASP which used up a lot of CPU time. Will need more computing time to continue these TS searches and continue the project. This needs to be approved and the final allocation amount decided upon. Thank You, The LCRC Accounts System

1 0

Re: [allocations-admins] [LCRC Accounts] Project Request: HELIOS
by Roberts, John E. 07 Jun '17

07 Jun '17

This project has been created with the correct storage amount and pushed to Blues. -- John Roberts Argonne National Laboratory CELS Systems jeroberts(a)anl.gov On 6/7/17, 2:22 PM, "allocations-admins on behalf of Bair, Raymond A." <allocations-admins-bounces(a)lcrc.anl.gov on behalf of rbair(a)anl.gov> wrote: P.S. 12TB is OK for storage, since we discussed it with them. However, if they want more later, we need to talk about disk purchase. ----------------------------------------- Ray Bair Argonne National Laboratory On 6/7/17, 2:17 PM, "allocations-admins on behalf of Bair, Raymond A." <allocations-admins-bounces(a)lcrc.anl.gov on behalf of rbair(a)anl.gov> wrote: This is a well written project plan. Let’s approve the 50K for Q3 now and the Committee can consider Q4 when it meets. Ray ----------------------------------------- Ray Bair Argonne National Laboratory On 6/6/17, 4:31 PM, "allocations-admins on behalf of accounts(a)lcrc.anl.gov" <allocations-admins-bounces(a)lcrc.anl.gov on behalf of accounts(a)lcrc.anl.gov> wrote: Hello, A new project on the LCRC cluster has been requested. Please forward the information on to the LCRC Allocation sub-committee. Applicant's name: Calem Hoffman Applicant's institution: ANL Applicant's division: Physics Project Name: HELIOS Project title: Real-Time Processing of Digitized Data from the ATLAS User Facility Associated funding: DOE Office of Science - Nuclear Physics Other Systems: None Science: The mission of the ATLAS User Facility is to provide the nuclear physics community with the most intense stable heavy-ion beams, and the associated experimental equipment, to allow for fundamental studies of the structure of nuclei. In particular, our community is focused on answering fundamental questions pertaining to the origin of the elements and how protons and neutrons behave under extreme conditions. The experiments performed at ATLAS range across many fundamental questions, while also touching on practical applications such as isotope production / harvesting and the robustness of materials to radiation. The proposed project aims to increase our data analysis and processing speed by more than ten-times our current capability with our in-division computing power. Utilizing the LCRC resource will allow for a large improvement in the physics output from one of the major user facilities here at ANL, specifically in the field of nuclear structure p hysics. As an initial input into the LCRC computing, we will focus on processing data from the HELIOS Spectrometer and its new data acquisition DigiOS to better understand the single-particle structure of nuclei through transfer reactions. This device has been chosen as it is the precursor to a device currently under design or order $2-4 Million for future use at the future Facility for Rare Isotope Beams under construction on the campus of Michigan State University. Project description: Summary: A major upgrade of the data taking capabilities has recently occurred for three major pieces of experimental equipment affiliated with the Argonne Tandem Linac Accelerator System (ATLAS) Facility located on-site here at Argonne. Specifically, we are now capable of digitizing all signals generated in our detectors systems, hence, not restricting our decision making about types of data collection to the hardware. While creating an opportunity for flexible and increased throughput, and ultimately deeper reaches into the structure of nuclei, it also has the side effect of generating larger amounts of data than our community is accustomed to handling. Therefore, we hope to leverage the availability of the LCRC for processing, both in real-time (eventually), as well as post-processing, data taken here at ANL from ATLAS. Goals: The initial goal of this project for the remainder of FY2017 will be to develop the infrastructure to send, process, and return data taken from actual experiments at ATLAS using the HELIOS Spectrometer and its digital data acquisition (DigiOS). Plan: Utilizing the individual 8000 hours provided by the LCRC, we have benchmarked our current analysis pipeline, and without any modifications to the software have identified improvement factors between 10 - 22 over our current analysis model. Hence, we will first solidify this pipeline within the project and develop some ease of use for real nuclear physics experiments. The current analysis pipeline is as follows: a) Data is collected at HELIOS a rate of ~5 MB / s over a 5 day period approximately once per month. Data is in form of 20 individual files with timestamps. - [~ 2 TB of data storage / month] b) Data must be passed to an LCRC machine. Not in real time at first. A gigabit transfer rate was already demonstrated from our PHY network using GLOBUS. We are pushing hard for a larger (20 gbit pipe in the near future). c) Data files must be inspected and sorted every hour [~20 GB / experiment run hr to process -> 1 core hr / experiment hr for each data sort] Uses a large amount of memory, current software is not developed for parallel processing. First will get this working then develop more parallel software. There are straight forward ways to make parallel however using SWIFT for example as the data can be broken up into ~1 hour â€œrunsâ€. We have demonstrated that this software can be run on blues. d) Time sorted data must be processed to generate events defined by a time window [~20 GB / experiment run hr to process -> 1 core hr / experiment hr for each data sort on blues]. Again, not presently setup for parallel computing but straightforward to run in batches, eventually can be modified for better use of multiple cores. We have demonstrated that this software can be run on blues. e) Final step is to generate physics results using the ROOT software [~20 GB / experiment run hr to process -> 1 core hr / experiment hr for each data sort]. This software has simple built-in features for using multiple cores on a single node. We have demonstrated that the software and the use of a full complement of cores on a single node is possible with our data. f) Output file from ROOT is small (<500 MB) and will be transferred back to local machines for display and additional analysis. At the beginning we estimate <25% of the jobs will be submitted for single-core use until we develop the proper batch submission software. However, these jobs will not be long in wall clock time (<1 hr each), and they will utilize the large memory capabilities of blues. The development of this software will be the highest priority once the complete analysis pipeline has been established. The information provided in a) above is what we used to determine our requested allocation for the completion of this fiscal year. Namely, 2 experiments spaced out over ~2 months, processing 20 GB / hr for 7 days with 2 TB of storage for the raw data and 6 TB storage for the processed data (time sorting essentially duplicates the data). At present, we need no additional software than has already been installed on blues. We foresee some development of the system through July and we have planned experiments that will utilize the resource starting in Mid-August and through September. We see no roadblocks with scalability or future software needs. The project will start with a limited number of users <10, however, it will scale up in the future when larger experiments make use of the resource. Initial project members will likely include: Calem Hoffman (PHY), Chris Peters (PHY), Torben Lauritsen (PHY), Michael Carpenter (PHY), and Sean Kuvin (UConn / PHY) Industry partnership: None Project URL: http://www.phy.anl.gov/atlas/helios https://wiki.anl.gov/heliosdaq/Main_Page Requested allocation: 300000 Q1: 0 Q2: 0 Q3: 50000 Q4: 250000 Justification: None Storage requirements: We request 12 TB of storage to accommodate one development experiment and two actual experiments along with the duplication of the raw data that takes place following the time sorting. Hence, ~4 TB / experiment through FY2017. The requester has used undetermined amount hours of their initial startup project. In addition to approving an initial amount, please specify a Category and Subcategory for this project. For a list of the current selection of approved categories, please see: https://wiki.lcrc.anl.gov/wiki/Processes/Categories Once the Allocation committee has approved the project, please go to the Project Management page to create it: https://accounts.lcrc.anl.gov/projects.php Thank You, The LCRC Accounts System _______________________________________________ allocations-admins mailing list allocations-admins(a)lcrc.anl.gov https://lists.lcrc.anl.gov/mailman/listinfo/allocations-admins _______________________________________________ allocations-admins mailing list allocations-admins(a)lcrc.anl.gov https://lists.lcrc.anl.gov/mailman/listinfo/allocations-admins

1 0

Re: [allocations-admins] [LCRC Accounts] Project Request: GTRI_FSI
by Roberts, John E. 07 Jun '17

07 Jun '17

This project has been created with the correct storage amount and pushed to Blues. -- John Roberts Argonne National Laboratory CELS Systems jeroberts(a)anl.gov On 6/7/17, 2:23 PM, "allocations-admins on behalf of Bair, Raymond A." <allocations-admins-bounces(a)lcrc.anl.gov on behalf of rbair(a)anl.gov> wrote: Note that this project wants 4TB disk. ----------------------------------------- Ray Bair Argonne National Laboratory On 6/7/17, 2:19 PM, "allocations-admins on behalf of Bair, Raymond A." <allocations-admins-bounces(a)lcrc.anl.gov on behalf of rbair(a)anl.gov> wrote: Given that we are 3 weeks from the end of the quarter, I suggest approving 100K now for Q3 and leaving 300K for Q4 decision by the Committee. Ray ----------------------------------------- Ray Bair Argonne National Laboratory On 6/7/17, 11:33 AM, "allocations-admins on behalf of accounts(a)lcrc.anl.gov" <allocations-admins-bounces(a)lcrc.anl.gov on behalf of accounts(a)lcrc.anl.gov> wrote: Hello, A new project on the LCRC cluster has been requested. Please forward the information on to the LCRC Allocation sub-committee. Applicant's name: Yiqi Yu Applicant's institution: ANL Applicant's division: Nuclear engineering Project Name: GTRI_FSI Project title: High-fidelity 3-D Fluid-Structure Interaction Simulations Associated funding: DOE NNSA Other Systems: Science: Use large scale high-fidelity 3-D Fluid-Structure Simulations to evaluate the behavior Low Enrichment Fuel Plates which will replace current High Enrichment Fuel Plates in selected research reactors. Project description: The project will use the high fidelity codes Nek5000 and DIABLO developed as part of the DOE NEAMS program to perform large scale fluid structure simulations of experiments performed at the University of Missouri (MU) in support of the conversion of the MU research reactor from HEU to LEU fuel plates. The results will be compared with results of experiments and simulations performed with the commercial codes STAR-CCM+ and ABAQUS. Industry partnership: This project supports the conversion of the MU research reactor from HEU to LEU fuel plates. The HEU-to-LEU conversion program is supported by DOE NNSA. Project URL: Requested allocation: 400000 Q1: 0 Q2: 0 Q3: 200000 Q4: 200000 Justification: Storage requirements: 4T disk storage The requester has used undetermined amount hours of their initial startup project. In addition to approving an initial amount, please specify a Category and Subcategory for this project. For a list of the current selection of approved categories, please see: https://wiki.lcrc.anl.gov/wiki/Processes/Categories Once the Allocation committee has approved the project, please go to the Project Management page to create it: https://accounts.lcrc.anl.gov/projects.php Thank You, The LCRC Accounts System _______________________________________________ allocations-admins mailing list allocations-admins(a)lcrc.anl.gov https://lists.lcrc.anl.gov/mailman/listinfo/allocations-admins _______________________________________________ allocations-admins mailing list allocations-admins(a)lcrc.anl.gov https://lists.lcrc.anl.gov/mailman/listinfo/allocations-admins _______________________________________________ allocations-admins mailing list allocations-admins(a)lcrc.anl.gov https://lists.lcrc.anl.gov/mailman/listinfo/allocations-admins

1 0

Re: [allocations-admins] [LCRC Accounts] Project Request: GTRI_FSI
by Bair, Raymond A. 07 Jun '17

07 Jun '17

Note that this project wants 4TB disk. ----------------------------------------- Ray Bair Argonne National Laboratory On 6/7/17, 2:19 PM, "allocations-admins on behalf of Bair, Raymond A." <allocations-admins-bounces(a)lcrc.anl.gov on behalf of rbair(a)anl.gov> wrote: Given that we are 3 weeks from the end of the quarter, I suggest approving 100K now for Q3 and leaving 300K for Q4 decision by the Committee. Ray ----------------------------------------- Ray Bair Argonne National Laboratory On 6/7/17, 11:33 AM, "allocations-admins on behalf of accounts(a)lcrc.anl.gov" <allocations-admins-bounces(a)lcrc.anl.gov on behalf of accounts(a)lcrc.anl.gov> wrote: Hello, A new project on the LCRC cluster has been requested. Please forward the information on to the LCRC Allocation sub-committee. Applicant's name: Yiqi Yu Applicant's institution: ANL Applicant's division: Nuclear engineering Project Name: GTRI_FSI Project title: High-fidelity 3-D Fluid-Structure Interaction Simulations Associated funding: DOE NNSA Other Systems: Science: Use large scale high-fidelity 3-D Fluid-Structure Simulations to evaluate the behavior Low Enrichment Fuel Plates which will replace current High Enrichment Fuel Plates in selected research reactors. Project description: The project will use the high fidelity codes Nek5000 and DIABLO developed as part of the DOE NEAMS program to perform large scale fluid structure simulations of experiments performed at the University of Missouri (MU) in support of the conversion of the MU research reactor from HEU to LEU fuel plates. The results will be compared with results of experiments and simulations performed with the commercial codes STAR-CCM+ and ABAQUS. Industry partnership: This project supports the conversion of the MU research reactor from HEU to LEU fuel plates. The HEU-to-LEU conversion program is supported by DOE NNSA. Project URL: Requested allocation: 400000 Q1: 0 Q2: 0 Q3: 200000 Q4: 200000 Justification: Storage requirements: 4T disk storage The requester has used undetermined amount hours of their initial startup project. In addition to approving an initial amount, please specify a Category and Subcategory for this project. For a list of the current selection of approved categories, please see: https://wiki.lcrc.anl.gov/wiki/Processes/Categories Once the Allocation committee has approved the project, please go to the Project Management page to create it: https://accounts.lcrc.anl.gov/projects.php Thank You, The LCRC Accounts System _______________________________________________ allocations-admins mailing list allocations-admins(a)lcrc.anl.gov https://lists.lcrc.anl.gov/mailman/listinfo/allocations-admins _______________________________________________ allocations-admins mailing list allocations-admins(a)lcrc.anl.gov https://lists.lcrc.anl.gov/mailman/listinfo/allocations-admins

1 0

Re: [allocations-admins] [LCRC Accounts] Project Request: HELIOS
by Bair, Raymond A. 07 Jun '17

07 Jun '17

P.S. 12TB is OK for storage, since we discussed it with them. However, if they want more later, we need to talk about disk purchase. ----------------------------------------- Ray Bair Argonne National Laboratory On 6/7/17, 2:17 PM, "allocations-admins on behalf of Bair, Raymond A." <allocations-admins-bounces(a)lcrc.anl.gov on behalf of rbair(a)anl.gov> wrote: This is a well written project plan. Let’s approve the 50K for Q3 now and the Committee can consider Q4 when it meets. Ray ----------------------------------------- Ray Bair Argonne National Laboratory On 6/6/17, 4:31 PM, "allocations-admins on behalf of accounts(a)lcrc.anl.gov" <allocations-admins-bounces(a)lcrc.anl.gov on behalf of accounts(a)lcrc.anl.gov> wrote: Hello, A new project on the LCRC cluster has been requested. Please forward the information on to the LCRC Allocation sub-committee. Applicant's name: Calem Hoffman Applicant's institution: ANL Applicant's division: Physics Project Name: HELIOS Project title: Real-Time Processing of Digitized Data from the ATLAS User Facility Associated funding: DOE Office of Science - Nuclear Physics Other Systems: None Science: The mission of the ATLAS User Facility is to provide the nuclear physics community with the most intense stable heavy-ion beams, and the associated experimental equipment, to allow for fundamental studies of the structure of nuclei. In particular, our community is focused on answering fundamental questions pertaining to the origin of the elements and how protons and neutrons behave under extreme conditions. The experiments performed at ATLAS range across many fundamental questions, while also touching on practical applications such as isotope production / harvesting and the robustness of materials to radiation. The proposed project aims to increase our data analysis and processing speed by more than ten-times our current capability with our in-division computing power. Utilizing the LCRC resource will allow for a large improvement in the physics output from one of the major user facilities here at ANL, specifically in the field of nuclear structure p hysics. As an initial input into the LCRC computing, we will focus on processing data from the HELIOS Spectrometer and its new data acquisition DigiOS to better understand the single-particle structure of nuclei through transfer reactions. This device has been chosen as it is the precursor to a device currently under design or order $2-4 Million for future use at the future Facility for Rare Isotope Beams under construction on the campus of Michigan State University. Project description: Summary: A major upgrade of the data taking capabilities has recently occurred for three major pieces of experimental equipment affiliated with the Argonne Tandem Linac Accelerator System (ATLAS) Facility located on-site here at Argonne. Specifically, we are now capable of digitizing all signals generated in our detectors systems, hence, not restricting our decision making about types of data collection to the hardware. While creating an opportunity for flexible and increased throughput, and ultimately deeper reaches into the structure of nuclei, it also has the side effect of generating larger amounts of data than our community is accustomed to handling. Therefore, we hope to leverage the availability of the LCRC for processing, both in real-time (eventually), as well as post-processing, data taken here at ANL from ATLAS. Goals: The initial goal of this project for the remainder of FY2017 will be to develop the infrastructure to send, process, and return data taken from actual experiments at ATLAS using the HELIOS Spectrometer and its digital data acquisition (DigiOS). Plan: Utilizing the individual 8000 hours provided by the LCRC, we have benchmarked our current analysis pipeline, and without any modifications to the software have identified improvement factors between 10 - 22 over our current analysis model. Hence, we will first solidify this pipeline within the project and develop some ease of use for real nuclear physics experiments. The current analysis pipeline is as follows: a) Data is collected at HELIOS a rate of ~5 MB / s over a 5 day period approximately once per month. Data is in form of 20 individual files with timestamps. - [~ 2 TB of data storage / month] b) Data must be passed to an LCRC machine. Not in real time at first. A gigabit transfer rate was already demonstrated from our PHY network using GLOBUS. We are pushing hard for a larger (20 gbit pipe in the near future). c) Data files must be inspected and sorted every hour [~20 GB / experiment run hr to process -> 1 core hr / experiment hr for each data sort] Uses a large amount of memory, current software is not developed for parallel processing. First will get this working then develop more parallel software. There are straight forward ways to make parallel however using SWIFT for example as the data can be broken up into ~1 hour â€œrunsâ€. We have demonstrated that this software can be run on blues. d) Time sorted data must be processed to generate events defined by a time window [~20 GB / experiment run hr to process -> 1 core hr / experiment hr for each data sort on blues]. Again, not presently setup for parallel computing but straightforward to run in batches, eventually can be modified for better use of multiple cores. We have demonstrated that this software can be run on blues. e) Final step is to generate physics results using the ROOT software [~20 GB / experiment run hr to process -> 1 core hr / experiment hr for each data sort]. This software has simple built-in features for using multiple cores on a single node. We have demonstrated that the software and the use of a full complement of cores on a single node is possible with our data. f) Output file from ROOT is small (<500 MB) and will be transferred back to local machines for display and additional analysis. At the beginning we estimate <25% of the jobs will be submitted for single-core use until we develop the proper batch submission software. However, these jobs will not be long in wall clock time (<1 hr each), and they will utilize the large memory capabilities of blues. The development of this software will be the highest priority once the complete analysis pipeline has been established. The information provided in a) above is what we used to determine our requested allocation for the completion of this fiscal year. Namely, 2 experiments spaced out over ~2 months, processing 20 GB / hr for 7 days with 2 TB of storage for the raw data and 6 TB storage for the processed data (time sorting essentially duplicates the data). At present, we need no additional software than has already been installed on blues. We foresee some development of the system through July and we have planned experiments that will utilize the resource starting in Mid-August and through September. We see no roadblocks with scalability or future software needs. The project will start with a limited number of users <10, however, it will scale up in the future when larger experiments make use of the resource. Initial project members will likely include: Calem Hoffman (PHY), Chris Peters (PHY), Torben Lauritsen (PHY), Michael Carpenter (PHY), and Sean Kuvin (UConn / PHY) Industry partnership: None Project URL: http://www.phy.anl.gov/atlas/helios https://wiki.anl.gov/heliosdaq/Main_Page Requested allocation: 300000 Q1: 0 Q2: 0 Q3: 50000 Q4: 250000 Justification: None Storage requirements: We request 12 TB of storage to accommodate one development experiment and two actual experiments along with the duplication of the raw data that takes place following the time sorting. Hence, ~4 TB / experiment through FY2017. The requester has used undetermined amount hours of their initial startup project. In addition to approving an initial amount, please specify a Category and Subcategory for this project. For a list of the current selection of approved categories, please see: https://wiki.lcrc.anl.gov/wiki/Processes/Categories Once the Allocation committee has approved the project, please go to the Project Management page to create it: https://accounts.lcrc.anl.gov/projects.php Thank You, The LCRC Accounts System _______________________________________________ allocations-admins mailing list allocations-admins(a)lcrc.anl.gov https://lists.lcrc.anl.gov/mailman/listinfo/allocations-admins

1 0

Re: [allocations-admins] [LCRC Accounts] Project Request: HELIOS
by Bair, Raymond A. 07 Jun '17

07 Jun '17

I think 4TB is OK, presuming we are not short of space. ----------------------------------------- Ray Bair Argonne National Laboratory On 6/7/17, 2:19 PM, "allocations-admins on behalf of Roberts, John E." <allocations-admins-bounces(a)lcrc.anl.gov on behalf of jeroberts(a)anl.gov> wrote: Are we okay with the storage request? It’s quite large. -- John Roberts Argonne National Laboratory CELS Systems jeroberts(a)anl.gov On 6/7/17, 2:17 PM, "allocations-admins on behalf of Bair, Raymond A." <allocations-admins-bounces(a)lcrc.anl.gov on behalf of rbair(a)anl.gov> wrote: This is a well written project plan. Let’s approve the 50K for Q3 now and the Committee can consider Q4 when it meets. Ray ----------------------------------------- Ray Bair Argonne National Laboratory On 6/6/17, 4:31 PM, "allocations-admins on behalf of accounts(a)lcrc.anl.gov" <allocations-admins-bounces(a)lcrc.anl.gov on behalf of accounts(a)lcrc.anl.gov> wrote: Hello, A new project on the LCRC cluster has been requested. Please forward the information on to the LCRC Allocation sub-committee. Applicant's name: Calem Hoffman Applicant's institution: ANL Applicant's division: Physics Project Name: HELIOS Project title: Real-Time Processing of Digitized Data from the ATLAS User Facility Associated funding: DOE Office of Science - Nuclear Physics Other Systems: None Science: The mission of the ATLAS User Facility is to provide the nuclear physics community with the most intense stable heavy-ion beams, and the associated experimental equipment, to allow for fundamental studies of the structure of nuclei. In particular, our community is focused on answering fundamental questions pertaining to the origin of the elements and how protons and neutrons behave under extreme conditions. The experiments performed at ATLAS range across many fundamental questions, while also touching on practical applications such as isotope production / harvesting and the robustness of materials to radiation. The proposed project aims to increase our data analysis and processing speed by more than ten-times our current capability with our in-division computing power. Utilizing the LCRC resource will allow for a large improvement in the physics output from one of the major user facilities here at ANL, specifically in the field of nuclear structure p hysics. As an initial input into the LCRC computing, we will focus on processing data from the HELIOS Spectrometer and its new data acquisition DigiOS to better understand the single-particle structure of nuclei through transfer reactions. This device has been chosen as it is the precursor to a device currently under design or order $2-4 Million for future use at the future Facility for Rare Isotope Beams under construction on the campus of Michigan State University. Project description: Summary: A major upgrade of the data taking capabilities has recently occurred for three major pieces of experimental equipment affiliated with the Argonne Tandem Linac Accelerator System (ATLAS) Facility located on-site here at Argonne. Specifically, we are now capable of digitizing all signals generated in our detectors systems, hence, not restricting our decision making about types of data collection to the hardware. While creating an opportunity for flexible and increased throughput, and ultimately deeper reaches into the structure of nuclei, it also has the side effect of generating larger amounts of data than our community is accustomed to handling. Therefore, we hope to leverage the availability of the LCRC for processing, both in real-time (eventually), as well as post-processing, data taken here at ANL from ATLAS. Goals: The initial goal of this project for the remainder of FY2017 will be to develop the infrastructure to send, process, and return data taken from actual experiments at ATLAS using the HELIOS Spectrometer and its digital data acquisition (DigiOS). Plan: Utilizing the individual 8000 hours provided by the LCRC, we have benchmarked our current analysis pipeline, and without any modifications to the software have identified improvement factors between 10 - 22 over our current analysis model. Hence, we will first solidify this pipeline within the project and develop some ease of use for real nuclear physics experiments. The current analysis pipeline is as follows: a) Data is collected at HELIOS a rate of ~5 MB / s over a 5 day period approximately once per month. Data is in form of 20 individual files with timestamps. - [~ 2 TB of data storage / month] b) Data must be passed to an LCRC machine. Not in real time at first. A gigabit transfer rate was already demonstrated from our PHY network using GLOBUS. We are pushing hard for a larger (20 gbit pipe in the near future). c) Data files must be inspected and sorted every hour [~20 GB / experiment run hr to process -> 1 core hr / experiment hr for each data sort] Uses a large amount of memory, current software is not developed for parallel processing. First will get this working then develop more parallel software. There are straight forward ways to make parallel however using SWIFT for example as the data can be broken up into ~1 hour â€œrunsâ€. We have demonstrated that this software can be run on blues. d) Time sorted data must be processed to generate events defined by a time window [~20 GB / experiment run hr to process -> 1 core hr / experiment hr for each data sort on blues]. Again, not presently setup for parallel computing but straightforward to run in batches, eventually can be modified for better use of multiple cores. We have demonstrated that this software can be run on blues. e) Final step is to generate physics results using the ROOT software [~20 GB / experiment run hr to process -> 1 core hr / experiment hr for each data sort]. This software has simple built-in features for using multiple cores on a single node. We have demonstrated that the software and the use of a full complement of cores on a single node is possible with our data. f) Output file from ROOT is small (<500 MB) and will be transferred back to local machines for display and additional analysis. At the beginning we estimate <25% of the jobs will be submitted for single-core use until we develop the proper batch submission software. However, these jobs will not be long in wall clock time (<1 hr each), and they will utilize the large memory capabilities of blues. The development of this software will be the highest priority once the complete analysis pipeline has been established. The information provided in a) above is what we used to determine our requested allocation for the completion of this fiscal year. Namely, 2 experiments spaced out over ~2 months, processing 20 GB / hr for 7 days with 2 TB of storage for the raw data and 6 TB storage for the processed data (time sorting essentially duplicates the data). At present, we need no additional software than has already been installed on blues. We foresee some development of the system through July and we have planned experiments that will utilize the resource starting in Mid-August and through September. We see no roadblocks with scalability or future software needs. The project will start with a limited number of users <10, however, it will scale up in the future when larger experiments make use of the resource. Initial project members will likely include: Calem Hoffman (PHY), Chris Peters (PHY), Torben Lauritsen (PHY), Michael Carpenter (PHY), and Sean Kuvin (UConn / PHY) Industry partnership: None Project URL: http://www.phy.anl.gov/atlas/helios https://wiki.anl.gov/heliosdaq/Main_Page Requested allocation: 300000 Q1: 0 Q2: 0 Q3: 50000 Q4: 250000 Justification: None Storage requirements: We request 12 TB of storage to accommodate one development experiment and two actual experiments along with the duplication of the raw data that takes place following the time sorting. Hence, ~4 TB / experiment through FY2017. The requester has used undetermined amount hours of their initial startup project. In addition to approving an initial amount, please specify a Category and Subcategory for this project. For a list of the current selection of approved categories, please see: https://wiki.lcrc.anl.gov/wiki/Processes/Categories Once the Allocation committee has approved the project, please go to the Project Management page to create it: https://accounts.lcrc.anl.gov/projects.php Thank You, The LCRC Accounts System _______________________________________________ allocations-admins mailing list allocations-admins(a)lcrc.anl.gov https://lists.lcrc.anl.gov/mailman/listinfo/allocations-admins _______________________________________________ allocations-admins mailing list allocations-admins(a)lcrc.anl.gov https://lists.lcrc.anl.gov/mailman/listinfo/allocations-admins

1 0

Re: [allocations-admins] [LCRC Accounts] Project Request: GTRI_FSI
by Bair, Raymond A. 07 Jun '17

07 Jun '17

Given that we are 3 weeks from the end of the quarter, I suggest approving 100K now for Q3 and leaving 300K for Q4 decision by the Committee. Ray ----------------------------------------- Ray Bair Argonne National Laboratory On 6/7/17, 11:33 AM, "allocations-admins on behalf of accounts(a)lcrc.anl.gov" <allocations-admins-bounces(a)lcrc.anl.gov on behalf of accounts(a)lcrc.anl.gov> wrote: Hello, A new project on the LCRC cluster has been requested. Please forward the information on to the LCRC Allocation sub-committee. Applicant's name: Yiqi Yu Applicant's institution: ANL Applicant's division: Nuclear engineering Project Name: GTRI_FSI Project title: High-fidelity 3-D Fluid-Structure Interaction Simulations Associated funding: DOE NNSA Other Systems: Science: Use large scale high-fidelity 3-D Fluid-Structure Simulations to evaluate the behavior Low Enrichment Fuel Plates which will replace current High Enrichment Fuel Plates in selected research reactors. Project description: The project will use the high fidelity codes Nek5000 and DIABLO developed as part of the DOE NEAMS program to perform large scale fluid structure simulations of experiments performed at the University of Missouri (MU) in support of the conversion of the MU research reactor from HEU to LEU fuel plates. The results will be compared with results of experiments and simulations performed with the commercial codes STAR-CCM+ and ABAQUS. Industry partnership: This project supports the conversion of the MU research reactor from HEU to LEU fuel plates. The HEU-to-LEU conversion program is supported by DOE NNSA. Project URL: Requested allocation: 400000 Q1: 0 Q2: 0 Q3: 200000 Q4: 200000 Justification: Storage requirements: 4T disk storage The requester has used undetermined amount hours of their initial startup project. In addition to approving an initial amount, please specify a Category and Subcategory for this project. For a list of the current selection of approved categories, please see: https://wiki.lcrc.anl.gov/wiki/Processes/Categories Once the Allocation committee has approved the project, please go to the Project Management page to create it: https://accounts.lcrc.anl.gov/projects.php Thank You, The LCRC Accounts System _______________________________________________ allocations-admins mailing list allocations-admins(a)lcrc.anl.gov https://lists.lcrc.anl.gov/mailman/listinfo/allocations-admins

1 0

Re: [allocations-admins] [LCRC Accounts] Project Request: HELIOS
by Roberts, John E. 07 Jun '17

07 Jun '17

Are we okay with the storage request? It’s quite large. -- John Roberts Argonne National Laboratory CELS Systems jeroberts(a)anl.gov On 6/7/17, 2:17 PM, "allocations-admins on behalf of Bair, Raymond A." <allocations-admins-bounces(a)lcrc.anl.gov on behalf of rbair(a)anl.gov> wrote: This is a well written project plan. Let’s approve the 50K for Q3 now and the Committee can consider Q4 when it meets. Ray ----------------------------------------- Ray Bair Argonne National Laboratory On 6/6/17, 4:31 PM, "allocations-admins on behalf of accounts(a)lcrc.anl.gov" <allocations-admins-bounces(a)lcrc.anl.gov on behalf of accounts(a)lcrc.anl.gov> wrote: Hello, A new project on the LCRC cluster has been requested. Please forward the information on to the LCRC Allocation sub-committee. Applicant's name: Calem Hoffman Applicant's institution: ANL Applicant's division: Physics Project Name: HELIOS Project title: Real-Time Processing of Digitized Data from the ATLAS User Facility Associated funding: DOE Office of Science - Nuclear Physics Other Systems: None Science: The mission of the ATLAS User Facility is to provide the nuclear physics community with the most intense stable heavy-ion beams, and the associated experimental equipment, to allow for fundamental studies of the structure of nuclei. In particular, our community is focused on answering fundamental questions pertaining to the origin of the elements and how protons and neutrons behave under extreme conditions. The experiments performed at ATLAS range across many fundamental questions, while also touching on practical applications such as isotope production / harvesting and the robustness of materials to radiation. The proposed project aims to increase our data analysis and processing speed by more than ten-times our current capability with our in-division computing power. Utilizing the LCRC resource will allow for a large improvement in the physics output from one of the major user facilities here at ANL, specifically in the field of nuclear structure p hysics. As an initial input into the LCRC computing, we will focus on processing data from the HELIOS Spectrometer and its new data acquisition DigiOS to better understand the single-particle structure of nuclei through transfer reactions. This device has been chosen as it is the precursor to a device currently under design or order $2-4 Million for future use at the future Facility for Rare Isotope Beams under construction on the campus of Michigan State University. Project description: Summary: A major upgrade of the data taking capabilities has recently occurred for three major pieces of experimental equipment affiliated with the Argonne Tandem Linac Accelerator System (ATLAS) Facility located on-site here at Argonne. Specifically, we are now capable of digitizing all signals generated in our detectors systems, hence, not restricting our decision making about types of data collection to the hardware. While creating an opportunity for flexible and increased throughput, and ultimately deeper reaches into the structure of nuclei, it also has the side effect of generating larger amounts of data than our community is accustomed to handling. Therefore, we hope to leverage the availability of the LCRC for processing, both in real-time (eventually), as well as post-processing, data taken here at ANL from ATLAS. Goals: The initial goal of this project for the remainder of FY2017 will be to develop the infrastructure to send, process, and return data taken from actual experiments at ATLAS using the HELIOS Spectrometer and its digital data acquisition (DigiOS). Plan: Utilizing the individual 8000 hours provided by the LCRC, we have benchmarked our current analysis pipeline, and without any modifications to the software have identified improvement factors between 10 - 22 over our current analysis model. Hence, we will first solidify this pipeline within the project and develop some ease of use for real nuclear physics experiments. The current analysis pipeline is as follows: a) Data is collected at HELIOS a rate of ~5 MB / s over a 5 day period approximately once per month. Data is in form of 20 individual files with timestamps. - [~ 2 TB of data storage / month] b) Data must be passed to an LCRC machine. Not in real time at first. A gigabit transfer rate was already demonstrated from our PHY network using GLOBUS. We are pushing hard for a larger (20 gbit pipe in the near future). c) Data files must be inspected and sorted every hour [~20 GB / experiment run hr to process -> 1 core hr / experiment hr for each data sort] Uses a large amount of memory, current software is not developed for parallel processing. First will get this working then develop more parallel software. There are straight forward ways to make parallel however using SWIFT for example as the data can be broken up into ~1 hour â€œrunsâ€. We have demonstrated that this software can be run on blues. d) Time sorted data must be processed to generate events defined by a time window [~20 GB / experiment run hr to process -> 1 core hr / experiment hr for each data sort on blues]. Again, not presently setup for parallel computing but straightforward to run in batches, eventually can be modified for better use of multiple cores. We have demonstrated that this software can be run on blues. e) Final step is to generate physics results using the ROOT software [~20 GB / experiment run hr to process -> 1 core hr / experiment hr for each data sort]. This software has simple built-in features for using multiple cores on a single node. We have demonstrated that the software and the use of a full complement of cores on a single node is possible with our data. f) Output file from ROOT is small (<500 MB) and will be transferred back to local machines for display and additional analysis. At the beginning we estimate <25% of the jobs will be submitted for single-core use until we develop the proper batch submission software. However, these jobs will not be long in wall clock time (<1 hr each), and they will utilize the large memory capabilities of blues. The development of this software will be the highest priority once the complete analysis pipeline has been established. The information provided in a) above is what we used to determine our requested allocation for the completion of this fiscal year. Namely, 2 experiments spaced out over ~2 months, processing 20 GB / hr for 7 days with 2 TB of storage for the raw data and 6 TB storage for the processed data (time sorting essentially duplicates the data). At present, we need no additional software than has already been installed on blues. We foresee some development of the system through July and we have planned experiments that will utilize the resource starting in Mid-August and through September. We see no roadblocks with scalability or future software needs. The project will start with a limited number of users <10, however, it will scale up in the future when larger experiments make use of the resource. Initial project members will likely include: Calem Hoffman (PHY), Chris Peters (PHY), Torben Lauritsen (PHY), Michael Carpenter (PHY), and Sean Kuvin (UConn / PHY) Industry partnership: None Project URL: http://www.phy.anl.gov/atlas/helios https://wiki.anl.gov/heliosdaq/Main_Page Requested allocation: 300000 Q1: 0 Q2: 0 Q3: 50000 Q4: 250000 Justification: None Storage requirements: We request 12 TB of storage to accommodate one development experiment and two actual experiments along with the duplication of the raw data that takes place following the time sorting. Hence, ~4 TB / experiment through FY2017. The requester has used undetermined amount hours of their initial startup project. In addition to approving an initial amount, please specify a Category and Subcategory for this project. For a list of the current selection of approved categories, please see: https://wiki.lcrc.anl.gov/wiki/Processes/Categories Once the Allocation committee has approved the project, please go to the Project Management page to create it: https://accounts.lcrc.anl.gov/projects.php Thank You, The LCRC Accounts System _______________________________________________ allocations-admins mailing list allocations-admins(a)lcrc.anl.gov https://lists.lcrc.anl.gov/mailman/listinfo/allocations-admins

1 0