psource_ncfile

asked 2019-09-26 14:46:03 +0100

Hi all,

After create my river runoff file using the make_runoff, I found the following error:

Runoff Data File: /data/croco-v1.0/Run/CROCO_FILES/croco_runoff.nc 1 Number of point sources READ_INP ERROR while reading block with keyword 'psource_ncfile'.

My cppdefs.h is:

                  /* Point Sources - Rivers */

undef PSOURCE

define PSOURCE_NCFILE

ifdef PSOURCE_NCFILE

define PSOURCE_NCFILE_TS

endif

And my croco.in:

psource: Nsrc Isrc Jsrc Dsrc Qbar [m3/s] Lsrc Tsrc

        0
              192   278   1    700.            T T      25. 0.

psource_ncfile: Nsrc Isrc Jsrc Dsrc qbardir Lsrc Tsrc runoff file name

            /data/croco-v1.0/Run/CROCO_FILES/croco_runoff.nc
            1
                    192  278  0  1  T  T  25.0  0.0

Any suggestion?

edit retag flag offensive close merge delete

add a comment

0

answered 2019-10-07 14:50:53 +0100

angelolemos
1

Thank you! Its working!

edit flag offensive delete link

add a comment

0

answered 2019-10-02 07:34:48 +0100

Matthieu.C
1

You forgot the * between 30 and T (see attached file)C:\fakepath\croco.in

edit flag offensive delete link

add a comment

0

answered 2019-10-02 00:16:37 +0100

angelolemos
1

Thank you Matthieu,

Unfortunately it did not work. My new last line is:

192 278 0 1 30T 30T 25.0 0.0

Follow attached the new file. Any suggestions are welcome. C:\fakepath\croco_inter.in

edit flag offensive delete link

add a comment

0

answered 2019-10-01 16:04:53 +0100

Matthieu.C
1

updated 2019-10-01 16:05:46 +0100

Hello, Could you try to replace your last line for psource_ncfile in croco.in by :

192 278 0 1 30T 30T 25.0 0.0

edit flag offensive delete link

add a comment

0

answered 2019-10-01 15:07:17 +0100

angelolemos
1

Thank you Camila,

Follow attached my croco.in. I did not see error about number of spaces between words or text layout.

Could you please clarify for me?

I have been trying different layouts.

C:\fakepath\croco_inter.in

edit flag offensive delete link

add a comment

0

answered 2019-09-30 02:00:37 +0100

camila
11

Hi, I got that error eventually when running with variable discharges. In my case at least I had some errors in the .in file, the number of spaces between words or some other text error.