error in routine open_file (error code 2) – in #10: INT2LM

in #10: INT2LM

<p> Hello, </p> <p> I am running the <span class="caps"> CCLM </span> in a model chain. <br/> Everything went fine, but now all of a sudden I get an error in the <strong> int2lm </strong> step: </p> <p> In month 06/2003 after successful opening all necessary input <strong> lffd*-files, and writing output *lbfd*-files til 2003070100 the program tries to open an *lfsd2003070103 </strong> file, which obviously does not exist (and doesn’t have to): </p> <pre> OPEN: ncdf-file: .../input/int2lm/2003_06/lffd2003070100.nc CLOSING ncdf FILE org_vert_inter_lm : Boundary layer height in COARSE layer # : 24 OPEN: ncdf-file: .../output/int2lm/2003_06/lbfd2003070100.nc CLOSING ncdf FILE OPEN: ncdf-file: .../input/int2lm/2003_06/lfsd2003070103.nc No such file or directory *------------------------------------------------------------* * PROGRAM TERMINATED BECAUSE OF ERRORS DETECTED * IN ROUTINE: open_file * * ERROR CODE is 2 * *------------------------------------------------------------* </pre> <p> Neither int2lm nor model configuration has been changed in the meantime. <br/> int2lm version is 1.10_clm14 (model version is 4.8_clm19) </p> <p> Thanks! </p>

  @redc_migration in #5ce81a7

<p> Hello, </p> <p> I am running the <span class="caps"> CCLM </span> in a model chain. <br/> Everything went fine, but now all of a sudden I get an error in the <strong> int2lm </strong> step: </p> <p> In month 06/2003 after successful opening all necessary input <strong> lffd*-files, and writing output *lbfd*-files til 2003070100 the program tries to open an *lfsd2003070103 </strong> file, which obviously does not exist (and doesn’t have to): </p> <pre> OPEN: ncdf-file: .../input/int2lm/2003_06/lffd2003070100.nc CLOSING ncdf FILE org_vert_inter_lm : Boundary layer height in COARSE layer # : 24 OPEN: ncdf-file: .../output/int2lm/2003_06/lbfd2003070100.nc CLOSING ncdf FILE OPEN: ncdf-file: .../input/int2lm/2003_06/lfsd2003070103.nc No such file or directory *------------------------------------------------------------* * PROGRAM TERMINATED BECAUSE OF ERRORS DETECTED * IN ROUTINE: open_file * * ERROR CODE is 2 * *------------------------------------------------------------* </pre> <p> Neither int2lm nor model configuration has been changed in the meantime. <br/> int2lm version is 1.10_clm14 (model version is 4.8_clm19) </p> <p> Thanks! </p>

error in routine open_file (error code 2)

re wrote

Hello,

I am running the CCLM in a model chain.
Everything went fine, but now all of a sudden I get an error in the int2lm step:

In month 06/2003 after successful opening all necessary input lffd*-files, and writing output *lbfd*-files til 2003070100 the program tries to open an *lfsd2003070103 file, which obviously does not exist (and doesn’t have to): 

 OPEN: ncdf-file: 
 .../input/int2lm/2003_06/lffd2003070100.nc
 CLOSING ncdf FILE
 org_vert_inter_lm        : Boundary layer height in COARSE layer # :
 24
 OPEN: ncdf-file: 
 .../output/int2lm/2003_06/lbfd2003070100.nc
 CLOSING ncdf FILE
 OPEN: ncdf-file: 
 .../input/int2lm/2003_06/lfsd2003070103.nc
 No such file or directory
 *------------------------------------------------------------*
 *    PROGRAM TERMINATED BECAUSE OF ERRORS DETECTED
 *              IN ROUTINE:   open_file
 *
 *    ERROR CODE is            2
 *    
 *------------------------------------------------------------*

Neither int2lm nor model configuration has been changed in the meantime.
int2lm version is 1.10_clm14 (model version is 4.8_clm19)

Thanks!

View in channel
<p> I assume that the file lffd2003070103.nc does not exist, at least not in that directory from which INT2LM reads these lffd-files. </p> <p> Hans-Juergen </p>

  @hans-jürgenpanitz in #9e7a774

<p> I assume that the file lffd2003070103.nc does not exist, at least not in that directory from which INT2LM reads these lffd-files. </p> <p> Hans-Juergen </p>
HP replied

I assume that the file lffd2003070103.nc does not exist, at least not in that directory from which INT2LM reads these lffd-files.

Hans-Juergen

View in channel
<p> Thanks. <br/> But as I wrote, it is for June 2003. So the last file being opened should be the <strong> 00z </strong> file of the next month: lffd2003070100. </p> <p> Instead it <strong> additionaly </strong> tries to open the file lfsd2003070103, i.e. wrong/unclear file header <strong> lfsd </strong> plus a not necessary timestep. <br/> Of course this file is not in the directory. But why should it exist in that directory (for June) at all? <br/> As I said all int2lm runs before worked fine without such a file. </p> <p> The question is why int2lm now demands this file? </p>

  @redc_migration in #65110b1

<p> Thanks. <br/> But as I wrote, it is for June 2003. So the last file being opened should be the <strong> 00z </strong> file of the next month: lffd2003070100. </p> <p> Instead it <strong> additionaly </strong> tries to open the file lfsd2003070103, i.e. wrong/unclear file header <strong> lfsd </strong> plus a not necessary timestep. <br/> Of course this file is not in the directory. But why should it exist in that directory (for June) at all? <br/> As I said all int2lm runs before worked fine without such a file. </p> <p> The question is why int2lm now demands this file? </p>
re replied

Thanks.
But as I wrote, it is for June 2003. So the last file being opened should be the 00z file of the next month: lffd2003070100.

Instead it additionaly tries to open the file lfsd2003070103, i.e. wrong/unclear file header lfsd plus a not necessary timestep.
Of course this file is not in the directory. But why should it exist in that directory (for June) at all?
As I said all int2lm runs before worked fine without such a file.

The question is why int2lm now demands this file?

View in channel
<p> Can you provide the files <span class="caps"> INPUT </span> and <span class="caps"> OUTPUT </span> ? </p>

  @burkhardtrockel in #f077491

<p> Can you provide the files <span class="caps"> INPUT </span> and <span class="caps"> OUTPUT </span> ? </p>
BR replied

Can you provide the files INPUT and OUTPUT ?

View in channel
<p> Burkhardt Rockel wrote: <br/> &gt; Can you provide the files <span class="caps"> INPUT </span> and <span class="caps"> OUTPUT </span> ? </p> <p> Thanks. Files are attached. </p>

  @redc_migration in #1499aff

<p> Burkhardt Rockel wrote: <br/> &gt; Can you provide the files <span class="caps"> INPUT </span> and <span class="caps"> OUTPUT </span> ? </p> <p> Thanks. Files are attached. </p>
re replied

Burkhardt Rockel wrote:
> Can you provide the files INPUT and OUTPUT ?

Thanks. Files are attached.

View in channel
<p> ydate_ini=‘2003060100’, hstart=0.0, hstop=5136, hincbound=3, <br/> is not just for June, it goes until 2004010100 <br/> If you want only June you need to set <br/> ydate_ini=‘2003060100’, hstart=0.0, hstop=720, hincbound=3, </p>

  @burkhardtrockel in #442ad0e

<p> ydate_ini=‘2003060100’, hstart=0.0, hstop=5136, hincbound=3, <br/> is not just for June, it goes until 2004010100 <br/> If you want only June you need to set <br/> ydate_ini=‘2003060100’, hstart=0.0, hstop=720, hincbound=3, </p>
BR replied

ydate_ini=‘2003060100’, hstart=0.0, hstop=5136, hincbound=3,
is not just for June, it goes until 2004010100
If you want only June you need to set
ydate_ini=‘2003060100’, hstart=0.0, hstop=720, hincbound=3,

View in channel
<p> Ok. <br/> Do you have an idea, how this could happen since I run the model in chain mode? <br/> And I didn’t change the configuration in the meantime. </p>

  @redc_migration in #73608fb

<p> Ok. <br/> Do you have an idea, how this could happen since I run the model in chain mode? <br/> And I didn’t change the configuration in the meantime. </p>
re replied

Ok.
Do you have an idea, how this could happen since I run the model in chain mode?
And I didn’t change the configuration in the meantime.

View in channel
<p> This can normally not happen. <br/> In the int2lm.job.tmpl after the line <br/> <pre> HSTOP=$(<code>{UTILS_BINDIR}/cfu get_hours </code>{CURRENT_DATE} <code>{NEXT_DATE} </code>{ITYPE_CALENDAR}) </pre> <br/> you may put an echo: <br/> <pre><br/> echo <code>{CURRENT_DATE} </code>{NEXT_DATE} <code>{ITYPE_CALENDAR} $HSTOP &lt;/pre&gt; run the command &lt;pre&gt; subchain int2lm 2003060100 &lt;/pre&gt; and check whether </code>@{CURRENT_DATE}@, <code></code>{NEXT_DATE}@ and <code>$HSTOP</code> have the right values. <br/> In your case <code></code>{NEXT_DATE}@ must have the value 2003070100.</pre> </p>

  @burkhardtrockel in #3445dc2

<p> This can normally not happen. <br/> In the int2lm.job.tmpl after the line <br/> <pre> HSTOP=$(<code>{UTILS_BINDIR}/cfu get_hours </code>{CURRENT_DATE} <code>{NEXT_DATE} </code>{ITYPE_CALENDAR}) </pre> <br/> you may put an echo: <br/> <pre><br/> echo <code>{CURRENT_DATE} </code>{NEXT_DATE} <code>{ITYPE_CALENDAR} $HSTOP &lt;/pre&gt; run the command &lt;pre&gt; subchain int2lm 2003060100 &lt;/pre&gt; and check whether </code>@{CURRENT_DATE}@, <code></code>{NEXT_DATE}@ and <code>$HSTOP</code> have the right values. <br/> In your case <code></code>{NEXT_DATE}@ must have the value 2003070100.</pre> </p>
BR replied

This can normally not happen.
In the int2lm.job.tmpl after the line 

HSTOP=$({UTILS_BINDIR}/cfu get_hours {CURRENT_DATE} {NEXT_DATE} {ITYPE_CALENDAR})

you may put an echo: 


echo  {CURRENT_DATE} {NEXT_DATE} {ITYPE_CALENDAR} $HSTOP
</pre>
run the command
<pre>
subchain int2lm 2003060100
</pre>
and check whether @{CURRENT_DATE}@, {NEXT_DATE}@ and $HSTOP have the right values. 

In your case {NEXT_DATE}@ must have the value 2003070100.

View in channel
<p> Now it works again. @{NEXT_DATE} was 2003070100 as supposed. <br/> Though I have no clue why this happened. </p> <p> Anyway. Thanks for your fast help. </p> <p> Alexander </p>

  @redc_migration in #a47dfeb

<p> Now it works again. @{NEXT_DATE} was 2003070100 as supposed. <br/> Though I have no clue why this happened. </p> <p> Anyway. Thanks for your fast help. </p> <p> Alexander </p>
re replied

Now it works again. @{NEXT_DATE} was 2003070100 as supposed.
Though I have no clue why this happened.

Anyway. Thanks for your fast help.

Alexander

View in channel