Wrong IMAS DD version in `STEP_SPP_001_EBCC_freeboundary.nc`

Open
#3 2 comments 0 reactions 1 assignee View on GitHub

@theo-brown is already working on this.

Since Feb 23, 2026.

Assessment

This issue has not been assessed yet.

Description

When running ncdump STEP_SPP_001_EBCC_freeboundary.nc | grep .data_dictionary I get the following output, implying that the data uses version 4.0.0 of the IMAS data dictionary:

:data_dictionary_version = "4.0.0" ;
        string ids_properties.version_put.data_dictionary ;
                string ids_properties.version_put.data_dictionary:_FillValue = "" ;
                ids_properties.version_put.data_dictionary:documentation = "Version of Data Dictionary used to PUT this IDS" ;
     ids_properties.version_put.data_dictionary = "4.0.0" ;
        string ids_properties.version_put.data_dictionary ;
                string ids_properties.version_put.data_dictionary:_FillValue = "" ;
                ids_properties.version_put.data_dictionary:documentation = "Version of Data Dictionary used to PUT this IDS" ;
     ids_properties.version_put.data_dictionary = "4.0.0" ;
        string ids_properties.version_put.data_dictionary ;
                string ids_properties.version_put.data_dictionary:_FillValue = "" ;
                ids_properties.version_put.data_dictionary:documentation = "Version of Data Dictionary used to PUT this IDS" ;
     ids_properties.version_put.data_dictionary = "4.0.0" ;

I believe this is wrong for two reasons:

  1. @fcasson states in #2 that the data dictionary version is 3.x
  2. The equilibrium data is not consistent with COCOS 17 (which would be required for it to be IMAS DD version 4 https://imas-data-dictionary.readthedocs.io/en/latest/cocos.html#cocos)
Dominant language
Jupyter Notebook
Stars
7
Forks
2
PR merge metrics
No merged PRs in 30d

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.