You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
A dataset will be generated using OPENFOAM or XRAGE depending on time of release. Using XRAGE initial amplitude and phase of a 10 mode pertubation will be altered to examine the impact of the evolution of the instability growth. All together that is 20 parameters for each run. Each run evolves over 40ns time period. Data is output as snapshots of the material and density file at each time step. In the unfortunate event that we cannot get a release for the data, we will use the JAG ICF data developed by Lawarence Livermore National Lab in collaboration with UCSD.
Note to the creator: please name the branch according to <branch_type>/<your_name>/<issue_number(s)_that_you_address>
If you address more than 1 issue with one branch, write each number with an underscore like the following: "chore/doruk/1_2"
But don't try to adress too many issues with a single branch!
The text was updated successfully, but these errors were encountered:
Also, please give details about the simulation and mention the parameters you plan to vary across different simulations (to facilitate further discussion if needed).
Description of item
A dataset will be generated using OPENFOAM or XRAGE depending on time of release. Using XRAGE initial amplitude and phase of a 10 mode pertubation will be altered to examine the impact of the evolution of the instability growth. All together that is 20 parameters for each run. Each run evolves over 40ns time period. Data is output as snapshots of the material and density file at each time step. In the unfortunate event that we cannot get a release for the data, we will use the JAG ICF data developed by Lawarence Livermore National Lab in collaboration with UCSD.
Correspondence: @cfkawa
Note to the creator: please name the branch according to <branch_type>/<your_name>/<issue_number(s)_that_you_address>
If you address more than 1 issue with one branch, write each number with an underscore like the following: "chore/doruk/1_2"
But don't try to adress too many issues with a single branch!
The text was updated successfully, but these errors were encountered: