# Objects not beeing found by XIOS (NEMO5.0)

**URL:** <https://nemo-ocean.discourse.group/t/objects-not-beeing-found-by-xios-nemo5-0/925>\
**Category:** Uncategorized\
**Tags:** XIOS\
**Created:** [3 July 2025 09:55 UTC](https://nemo-ocean.discourse.group/t/objects-not-beeing-found-by-xios-nemo5-0/925 "2025-07-03T09:55:53Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![Franziska](https://avatars.discourse-cdn.com/v4/letter/f/8797f3/32.png) [@Franziska](https://nemo-ocean.discourse.group/u/Franziska)\
**Post date:** [3 July 2025 09:55 UTC](https://nemo-ocean.discourse.group/t/objects-not-beeing-found-by-xios-nemo5-0/925/1 "2025-07-03T09:55:53Z")

</div>

Hi,

Note, I came across the below described issue before ([see ticket](https://nemo-ocean.discourse.group/t/nemov5-0-field-definition-required-altough-not-used-ice-suppresion-on-child-grid/824)) in a nested configuration, however, the “solution” doesn’t apply for my current configuration.

I encounter errors with objects not beeing found by XIOS(3) in a **ocean-atm coupled configuartion** , e.g.:  
`In file "object_factory_impl.hpp", function "static std::shared_ptr<_Tp> xios::CObjectFactory::GetObject(const StdString&) [with U = xios::CField; StdString = std::__cxx11::basic_string<char>]", line 76 -> [id = dvpn_mlt, U = field] object was not found.`

Irrespective of whether I activate the respective functionality (e.g. melt ponds; the first occurrence I get) or add respective variables to the output, I always end up with such errors.

All affected variables are treated similarly and should be only available if `iom_use`d  
Only when removing these dependencies (e.g. hard code `ll_diag_pnd = .TRUE.` in `icethd_pnd.F90`), the errors can be overcome.

The issue does not occur in an ocean-only, un-nested configuration.  
Having the [previously described](https://nemo-ocean.discourse.group/t/nemov5-0-field-definition-required-altough-not-used-ice-suppresion-on-child-grid/824) behaviour in mind, I assume conflicts between different contexts (here ocean and atmosphere?) but cannot pin that down from the xml-file side as it was possible for the nested configuration.

Any hint is very much appreciated.

Best regards  
Franziska

---

<div class="post-metadata">

**Author:** ![Franziska](https://avatars.discourse-cdn.com/v4/letter/f/8797f3/32.png) [@Franziska](https://nemo-ocean.discourse.group/u/Franziska)\
**Post date:** [16 December 2025 06:18 UTC](https://nemo-ocean.discourse.group/t/objects-not-beeing-found-by-xios-nemo5-0/925/2 "2025-12-16T06:18:42Z")

</div>

Hi,

I just saw the issue [**XIOS calls before context initialisation**]( [XIOS calls before context initialisation (#696) · Issues · NEMO Workspace / Nemo · GitLab](https://forge.nemo-ocean.eu/nemo/nemo/-/issues/696) and think this could be the actual cause of the behaviour I tried to describe above, which also appears with XIOS2 in (at least my) cases with multiple model components.  
Further affected routines are `diaptr.F90` `icedyn_rdgrft.F90` `icethd_pnd.F90` and `traldf.F90`.

Is the current recommendation to use the indicated XIOS revsions [r2857](https://forge.ipsl.fr/ioserver/changeset/2857) or [r2866](https://forge.ipsl.fr/ioserver/changeset/2866)? If so, is there a preferred one?