<html><head><meta http-equiv="content-type" content="text/html; charset=us-ascii"></head><body style="overflow-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;">Hi Fisher,<div><br></div><div>I recommend using (or at least trying) useSingleCpuIO = .TRUE. instead of globalFiles=.True. In my experience, this is faster and more robust if the data fits on one CPU/node.</div><div><br></div><div>For merging tiled mds-data, you could try to read the data into python with rdmds and write them with wrmds (both in MITgcmutils/mds.py</div><div><br></div><div>Martin</div><div><br id="lineBreakAtBeginningOfMessage"><div><br><blockquote type="cite"><div>On 7. Jul 2025, at 08:12, ht <ht.fisher@protonmail.com> wrote:</div><br class="Apple-interchange-newline"><div><meta http-equiv="Content-Type" content="text/html; charset=utf-8"><div style="font-family: Arial, sans-serif; font-size: 14px; background-color: rgb(255, 255, 255);"><br class="webkit-block-placeholder"></div><p data-start="345" data-end="360">Dear Community,</p><p data-start="362" data-end="456">I am currently conducting simulations using the MITgcm with a Cubed-Sphere grid configuration.</p><p data-start="458" data-end="682">In the past, I have read output data consisting of multiple <code data-start="518" data-end="525">.meta</code> files (e.g., <code data-start="539" data-end="556">XC.001.001.meta</code>, <code data-start="558" data-end="575">XC.002.001.meta</code>, etc.) using <code data-start="589" data-end="608">MITgcmutils.rdmds</code>, followed by applying my own regridding functions during post-processing.</p><p data-start="684" data-end="1083">Recently, I came across a Python package called <strong data-start="732" data-end="747">cubedsphere(<a href="https://github.com/AaronDavidSchneider/cubedsphere">https://github.com/AaronDavidSchneider/cubedsphere</a>)</strong>, which seems to offer a more streamlined workflow for handling Cubed-Sphere grids. However, it appears to rely on the existence of unified <code data-start="887" data-end="894">.meta</code> files such as <code data-start="909" data-end="918">XC.meta</code>, which are not generated by default in my MITgcm outputs. Similarly, the <code data-start="992" data-end="1009">open_mdsdataset</code> function in <strong data-start="1022" data-end="1033">xmitgcm</strong> also expects grid meta files in a unified format.</p><p data-start="1085" data-end="1322">I have since learned that setting <code data-start="1119" data-end="1141">globalFiles = .TRUE.</code> in <code data-start="1145" data-end="1157">input/data</code> allows MITgcm to generate single <code data-start="1191" data-end="1198">.meta</code> and <code data-start="1203" data-end="1210">.data</code> files per timestep, even with a Cubed-Sphere grid. This seems like a promising approach for future simulations.</p><p data-start="1324" data-end="1486">However, for simulations that I have already completed, the output files are split by tile (e.g., <code data-start="1422" data-end="1449">S.0000000000.001.001.meta</code>, <code data-start="1451" data-end="1478">S.0000000000.002.001.meta</code>, etc.).</p><p data-start="1488" data-end="1519">Therefore, I would like to ask:</p><ul data-start="1521" data-end="1721"><li data-start="1521" data-end="1721"><p data-start="1523" data-end="1721">Is there any recommended method or tool to combine these previously generated tiled output files into unified <code data-start="1633" data-end="1640">.meta</code> and <code data-start="1645" data-end="1652">.data</code> files (e.g., <code data-start="1666" data-end="1685">S.0000000000.meta</code>) after the simulation has finished?</p></li></ul><p data-start="1723" data-end="1824">Any advice, suggested tools, or workflows for this post-processing task would be greatly appreciated.</p><p data-start="1826" data-end="1872">Thank you very much for your time and support.</p><p data-start="1874" data-end="1896">Best regards,<br data-start="1887" data-end="1890">
Fisher</p><div data-start="1299" data-end="1345" style="font-family: Arial, sans-serif; font-size: 14px; margin-top: 14px; margin-bottom: 14px; background-color: rgb(255, 255, 255);"></div>_______________________________________________<br>MITgcm-support mailing list<br>MITgcm-support@mitgcm.org<br>http://mailman.mitgcm.org/mailman/listinfo/mitgcm-support<br></div></blockquote></div><br></div></body></html>