We can look into Doxygen (since it supports python and C++)
Note to the addressee: 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"
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!
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!
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!
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!
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!
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!
We will follow some unified practices during this project. Therefore there will be some standards.
I will create a folder for reference. @sahilbhola14 once I'm done with it, it'd be great if you can chime in to polish some details.
So far, the documentation is being done locally for which scripts are already available.
Is it possible to automate the doc build state using git actions?
Note to the addressee: 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"
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!
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!
OpenFOAM directly provides post-processing through the command line. Post-processing can be done in the conventional manner (after all the data is generated) or run-time post-processing may be done. time, vorticity, turbulence (etc), velocity, will all be quantities that we want to consider and store.
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!