Shots with a timebase greater than 300 are cut off using EFIT 18

MIT-PSFC / disruption-py

Workflow, modules, and submodules to populate SQL databases on multiple machines for disruption prediction analysis and beyond

https://mit-psfc.github.io/disruption-py/

MIT License

9 stars 0 forks source link

Shots with a timebase greater than 300 are cut off using EFIT 18 #108

Open lajz opened 6 months ago

lajz commented 6 months ago

Example shots: 1120131009, 1120516006, 1120503012, 1120509010

gtrevisan commented 6 months ago

could you provide further info?

lajz commented 6 months ago

It appears that the efit18 tree only holds up to 300 time slices (all data after that is cut off), which is highly problematic as it causes the timebase that we base off of the efit time to be missing data and I also assume causes us to lose efit data. You can see this cut off in jtraverser (for instance for shot 1120516006): Screenshot 2024-03-21 at 11 59 26 AM

gtrevisan commented 6 months ago

huh, okay.

in order to get the timebase, one solution would then be to manually craft the time array starting from the disruption time and the duration, but that still would not get us the efit18 quantities that got dropped!

lajz commented 6 months ago

Agreed, will investigate further to see if there is a work around