# MUSTANG model - climatology

**URL:** <https://forum.croco-ocean.org/t/mustang-model-climatology/692>\
**Category:** sediment\
**Created:** [May 7, 2024, 11:38pm UTC](https://forum.croco-ocean.org/t/mustang-model-climatology/692 "2024-05-07T23:38:27Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![limramirezmo](https://forum.croco-ocean.org/letter_avatar_proxy/v4/letter/l/ecccb3/32.png) [@limramirezmo](https://forum.croco-ocean.org/u/limramirezmo)\
**Post date:** [May 7, 2024, 11:38pm UTC](https://forum.croco-ocean.org/t/mustang-model-climatology/692/1 "2024-05-07T23:38:27Z")

</div>

Hello,  
Can I run the MUSTANG model under climatology conditions? If it’s possible, what steps should I take?  
I’ve attempted to run a scenario under climatology conditions activating MUSTANG and keeping the files in MUSTANG\_NAMELIST/\*.txt identical to those in the VILAINE scenario, but I encountered the following message:

“TOOL\_ORIGINDATE ERROR: Could not find any origin date in time var units. Time variable should follow the NetCDF CF format: ‘seconds(days) since YYYY-MM-DD hh:mm:ss’.”

Thanks  
Lina

---

<div class="post-metadata">

**Author:** ![limramirezmo](https://forum.croco-ocean.org/letter_avatar_proxy/v4/letter/l/ecccb3/32.png) [@limramirezmo](https://forum.croco-ocean.org/u/limramirezmo)\
**Post date:** [May 10, 2024, 1:06am UTC](https://forum.croco-ocean.org/t/mustang-model-climatology/692/2 "2024-05-10T01:06:30Z")

</div>

The previous error appears to be a configuration error in the input netCDF files, where some attributes are missing because I created these netCDF files with CROCO version 1.1, although I see that even CROCO version 1.3.1 doesn’t output these attributes by default.

However, I reached this conclusion by comparing the input files from the VILAINE case with my input files. This message doesn’t appear as frequently now, but it still pops up occasionally, even though the model is reading more information.

I have a question: Does the MUSTANG module only work with boundary input files of the **croco\_bry.nc** type and not with **croco\_clm.nc** type boundaries?  
I’ve attached the croco.log file.  
[croco\_log.txt](https://forum.croco-ocean.org/uploads/short-url/mbyWRpiQP1q8xDYhqKncG5JsY46.txt) (23.5 KB)

I appreciate any suggestions. Thank you.

---

<div class="post-metadata">

**Author:** ![slegac](https://forum.croco-ocean.org/user_avatar/forum.croco-ocean.org/slegac/32/267_2.png) [@slegac](https://forum.croco-ocean.org/u/slegac)\
**Post date:** [May 29, 2024, 7:23am UTC](https://forum.croco-ocean.org/t/mustang-model-climatology/692/3 "2024-05-29T07:23:17Z")

</div>

MUSTANG use the cpp keys #USE\_CALENDAR.

That is why you must define your time axis units attributes.

You can add attributes using ncatted netcdf command ([NCO 5.2.5-alpha02 User Guide](https://nco.sourceforge.net/nco.html#ncatted-netCDF-Attribute-Editor) ), here find an example :

```auto
ncatted -O -a units,ocean_time,m,c,'seconds since 2000-01-01 00:00:00' croco_ini_SODA_Y2005M01.nc 
ncatted -O -a units,scrum_time,m,c,'seconds since 2000-01-01 00:00:00' croco_ini_SODA_Y2005M01.nc 
ncatted -O -a units,bulk_time,m,c,'days since 2000-01-01 00:00:00' croco_blk_ERA5_Y2005M01.nc 
ncatted -O -a units,bry_time,m,c,'days since 2000-01-01 00:00:00' croco_bry_SODA_Y2005M01.nc

```

If your hydrodynamic simulation runs with USE\_CALENDAR you should not have this issue with MUSTANG.

---

<div class="post-metadata">

**Author:** ![limramirezmo](https://forum.croco-ocean.org/letter_avatar_proxy/v4/letter/l/ecccb3/32.png) [@limramirezmo](https://forum.croco-ocean.org/u/limramirezmo)\
**Post date:** [May 30, 2024, 7:49pm UTC](https://forum.croco-ocean.org/t/mustang-model-climatology/692/4 "2024-05-30T19:49:59Z")

</div>

Thank you, the hydrodynamics-only simulation was not using USE\_CALENDAR.

I see now that this key is important for using MUSTANG.

Thanks, I have already added the attributes to the bry and ini files, and it started running without any problems.
