The issue was raised in a meeting by @DavidPCoster and could finally be reproduced (not that it affects also IDStools and IMAS-Python installed in their develop version):
(venv23b) [hoeneno@98dci4-srv-1005 support]$ pip freeze|grep imas
imas-core==5.7.2
imas-data-dictionaries==4.1.1
imas-idstools==2.4.1
imas-python==2.3.0
(venv23b) [hoeneno@98dci4-srv-1005 support]$ idslist -u "imas://uda.iter.org:56565/uda?path=/work/imas/shared/imasdb/ITER/3/134174/117;backend=hdf5"
09:01:09 INFO Parsing data dictionary version 4.1.1 @dd_zip.py:89
List of IDSes
┏━━━━━━━━━━━━━━━━┳━━━━━━━━┳━━━━━━┓
┃ IDS ┃ SLICES ┃ TIME ┃
┡━━━━━━━━━━━━━━━━╇━━━━━━━━╇━━━━━━┩
│ core_profiles │ 0 │ [] │
│ core_sources │ 0 │ [] │
│ core_transport │ 0 │ [] │
│ edge_profiles │ 0 │ [] │
│ edge_sources │ 0 │ [] │
│ edge_transport │ 0 │ [] │
│ equilibrium │ 0 │ [] │
│ summary │ 0 │ [] │
└────────────────┴────────┴──────┘
Now the behavior was different with imas-python==2.1.0, giving a clue at the source of this problem: in version 2.2.0 was introduced the differed DD parsing, which, together with the special case of multi DD version and UDA.
The issue was raised in a meeting by @DavidPCoster and could finally be reproduced (not that it affects also IDStools and IMAS-Python installed in their
developversion):Now the behavior was different with imas-python==2.1.0, giving a clue at the source of this problem: in version 2.2.0 was introduced the differed DD parsing, which, together with the special case of multi DD version and UDA.
Now an immediate solution (or more a work-around as far as end-user is concerned) is to append
cache_mode=noneto the URI query: