Conversation
|
I think exactly like that, it's the same here: I believe that worked at some point. I will have a look. |
rettigl
left a comment
There was a problem hiding this comment.
This works for me:
"/ENTRY/CALIBRATION[transmission_correction]":{
"calibrated_axis": "@DaTa:angular0.data",
"transmission_function/@signal": "relative_intensity",
"transmission_function/@axes": "kinetic_energy",
"transmission_function/kinetic_energy": "@DaTa:angular0.data",
"transmission_function/kinetic_energy/@Units": "eV",
"transmission_function/relative_intensity": "@DaTa:angular0.data"
},
Changing @axes gives:
WARNING: The value at /ENTRY[entry]/CALIBRATION[transmission_correction]/transmission_function/@axes should be one of the following: ['kinetic_energy'].
|
But that is exactly the issue, In your implementation, How do we need to denote the enum of an array of strings in the application definition and how should we write it in the template? |
|
You are right, I will check again. |
|
This works for me: The axes is indeed supposed to be a list of strings inside the file, not a single string. |

@rettigl I am not sure how one would write this now, both on the appdef level and in the file. Do you have a good suggestion? Even with this approach here, it is failing when I write
['kinetic_energy']into the file