Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Feature Development - Time Dependence - Internally #153

Open
9 tasks
tyounkin opened this issue Dec 16, 2022 · 2 comments
Open
9 tasks

Feature Development - Time Dependence - Internally #153

tyounkin opened this issue Dec 16, 2022 · 2 comments
Assignees
Labels

Comments

@tyounkin
Copy link
Collaborator

tyounkin commented Dec 16, 2022

This issue is the high-level view of the development work going in to time-dependence.
Time-dependence is the tracking of time dependent erosion, impurity migration, and deposition of material and includes..

  • Build up examples in repository

    • ProtoMPEX
    • CPC example
    • Simple fluid theory
    • ITER He case
    • DiMES example
  • Time-dependent density tracking (persistent source)

  • time-dependent source

  • time-dependent SOLPS profiles (on SOLPS grid)

@tyounkin tyounkin added this to the Time dependence milestone Dec 16, 2022
@tyounkin tyounkin self-assigned this Dec 16, 2022
@tyounkin tyounkin added the test label Dec 16, 2022
@tyounkin
Copy link
Collaborator Author

Option for input should probably be an integer that corresponds to
0 - Off, no time dependence. Run in original GITR algorithm, solving steady state solution with persistent source
1 - On and use time-dependent density tracking (only)
2 - On and use time-dependent density tracking AND non-constant source (non-uniform particle initialization time)
3 - On and use time-dependent density tracking AND non-constant source AND time-varying background plasma profiles

@stonecoldhughes stonecoldhughes changed the title Feature Development - Time Dependence Feature Development - Time Dependence - Internally Jan 13, 2023
@tyounkin
Copy link
Collaborator Author

Rules for examples in the repository:

  1. File size - 200kb for an input deck maximum
  2. File type - text only, cfg files are fine, we want python to generate inputs.
  3. Processing/checking answers - need to have python text file
  4. Integration into ctest or different test harness - generate and test answers

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant