-
Notifications
You must be signed in to change notification settings - Fork 15
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
Added profiles from CAKE #236
base: master
Are you sure you want to change the base?
Conversation
AreWeDreaming
commented
Mar 8, 2023
- Ripped out other references to profiles needs to be reviewed carefully
- Ripped out other references to profiles needs to be reviewed carefully
"core_profiles.global_quantities.v_loop": { | ||
"COCOSIO": 11, | ||
"PYTHON": "core_profiles_global_quantities_data(ods, {pulse})" | ||
}, |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I had to rip this out to make it work. Putting it back in causes:
``core_profiles.profiles_1d.0.grid.rho_pol_norm has no data
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@orso82 Do you understand why @AreWeDreaming would get this error, if this is not removed?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Maybe core_profiles_global_quantities_data
looks at core_profiles.profiles_1d.0.grid.rho_pol_norm
for some reason, and that mapping was not in place?
}, | ||
"core_profiles.profiles_1d.:.electrons.temperature": { | ||
"TDI": "\\{PROFILES_tree}::TOP.PROFILES.ETEMPFIT", | ||
"treename": "{PROFILES_tree}" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Same here, but not because of errors but because of multiple sources for the same field. I don't know how to resolve this.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@orso82 How does one specify in the machine mappings when the same quantity is available via a variety of MDSplus trees? Maybe passing an argument to ods.open
that gets passed to the underlying new core_profiles_profile_1d
?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks promising.
"core_profiles.global_quantities.v_loop": { | ||
"COCOSIO": 11, | ||
"PYTHON": "core_profiles_global_quantities_data(ods, {pulse})" | ||
}, |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@orso82 Do you understand why @AreWeDreaming would get this error, if this is not removed?
}, | ||
"core_profiles.profiles_1d.:.electrons.temperature": { | ||
"TDI": "\\{PROFILES_tree}::TOP.PROFILES.ETEMPFIT", | ||
"treename": "{PROFILES_tree}" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@orso82 How does one specify in the machine mappings when the same quantity is available via a variety of MDSplus trees? Maybe passing an argument to ods.open
that gets passed to the underlying new core_profiles_profile_1d
?
See the "options" section in the "*.json" files to see how options can be passed to mapping functions. For example, you should be able to do: "__options__": {
"EFIT_tree": "EFIT01",
"PROFILES_tree": "ZIPFIT01",
"analysis_type": "CERQUICK",
"default_tree": "D3D",
"fast_ece": false,
"nref": 0,
"revision": "BLESSED"
},
...
"core_profiles.profiles_1d.:.electrons.density": {
"PYTHON": "core_profiles_profile_1d(ods, {pulse}, {PROFILES_tree})"
} which can then be passed with with ods.open("d3d", 133221, PROFILES_tree="mytree")
plot(ods['core_profiles.profiles_1d.0.electrons.density']) |
Should the ability to read ZIPFITS be retained? Are you sure there is nothing that depends on that? |
@orso82 Thanks for the example. I am not suggesting to removed anything, I was just confused about what to do and wanted to have an example for what I was struggling with when asking for help. I didn't realize that I need to move the zipfit mapping out of the .json file and into my new routine. I'll add an if-clause and the tree name as an argument. |
- The use of coniditionals seems to cause problems for the .json - Code could probably use some refactoring
The last commit has several problems:
|
|
Ok, so I managed to sort out all the problems I think. It seems that there were some minor errors that then became several weird problems. Now I can switch between |
- Removed GS error evolution plot
- Also added labels for ion
- Load missing equilibrium quantities via OMFIT - Added functions for improved unit and scale handling in plots - Added extra optional argument `omas_viewer` to equilibrium summary - It plots `p`, `q`, `j_tor`, and `chi^2` for diagnostics - Creates annotations for the `chi^2` plot with identifiers - Shows contraints for `j_tor` and `p` from `code.paramters`
- Moved functions needed by mappings to seprate file - Moved the machine mapping decorator to a utilities file - Moved MDS+ related routines into their own file - Added extra argument to pass `update_mapping` as an argument - Removed `compile` statement as it was causing trouble for the debugger
…mfit_profiles_mapping_for_d3d
Stale pull request message |
@AreWeDreaming should remove the |
Stale pull request message |