however this results in ValueError: Not an IMAS data type O:
ValueError: Not an IMAS data type O
```
Error in "OMFIT command box #18" at line 3
print(ods['pulse_schedule.position_control.x_point.:.z.reference.data'])
ValueError: Not an IMAS data type O
Press to see full error report...
Traceback (most recent call last):
File "/home/eldond/OMFIT-source/omfit/classes/OMFITx.py", line 4068, in manage_user_errors
tmp=command(**kw)
File "/home/eldond/OMFIT-source/omfit/utils_tk.py", line 1060, in GlobLoc_tk
return py.run(_relLoc=self.namespace, _OMFITscriptsDict=False, _OMFITconsoleDict=True, noGUI=None)
File "/home/eldond/OMFIT-source/omfit/classes/omfit_python.py", line 1082, in run
result = self.__run__(**kw)
File "/home/eldond/OMFIT-source/omfit/classes/omfit_python.py", line 930, in __run__
tmp = execGlobLoc(
File "/home/eldond/OMFIT-source/omfit/classes/omfit_python.py", line 129, in f_locked
return f(*args, **kw)
File "/home/eldond/OMFIT-source/omfit/classes/omfit_python.py", line 362, in execGlobLoc
exec(compile(execString, filename, "exec"), GlobLoc)
File "/home/eldond/tmp/eldond/eldond/OMFIT/OMFIT_2020-10-28_13_18_12_659490/project/OMFIT command box #18", line 3, in
print(ods['pulse_schedule.position_control.x_point.:.z.reference.data'])
File "/home/eldond/omas/omas/omas_core.py", line 1126, in __getitem__
return value.__getitem__(key[1:], cocos_and_coords)
File "/home/eldond/omas/omas/omas_core.py", line 1126, in __getitem__
return value.__getitem__(key[1:], cocos_and_coords)
File "/home/eldond/omas/omas/omas_core.py", line 1126, in __getitem__
return value.__getitem__(key[1:], cocos_and_coords)
File "/home/eldond/omas/omas/omas_core.py", line 1094, in __getitem__
raise ValueError('Not an IMAS data type %s' % dtype.char)
ValueError: Not an IMAS data type O
```
And I confirm that stripping the uncertainties returns ODS to expected behavior:
pulse_schedule.position_control.x_point[:].z.reference.data
is listed as having typeFLT_1D (uncertain)
on https://gafusion.github.io/omas/schema/schema_pulse%20schedule.html . So, it should be valid to assignAnd indeed this has been accepted and will print:
as expected. However, if the values were not uncertain, then the 0 should be replaceable with :, as in
however this results in
ValueError: Not an IMAS data type O
:ValueError: Not an IMAS data type O
``` Error in "OMFIT command box #18" at line 3 print(ods['pulse_schedule.position_control.x_point.:.z.reference.data']) ValueError: Not an IMAS data type O PressAnd I confirm that stripping the uncertainties returns ODS to expected behavior:
I need the uncertainties to carry tolerances mentioned in https://github.com/gafusion/OMFIT-source/issues/4811.