Using netcdf data for metforcing

[shaider2]

Hi,
I am using LIS 7.5.2 and NLDAS2 netcdf data for met forcing. Unfortunately, my simulation is failing. I have attached my log file, config file, and error file. It would be great if I could get some feedback on this.
lis.config.coldstart.2.txt
lislog_12km.0000.txt
slurm-10182782.out.txt
job.10187579.err.txt

[dmocko]

Hi @shaider2

The public releases do not yet have the NLDAS-2 netCDF metforcing capability.

We are actively working on a new public release and updating the testcases and scripts for the netCDF data.

Thanks for your patience.

[shaider2]

Hi @dmocko ,
Thank you so much for letting me know. As I urgently need some simulations, is there any probable pathway I can utilize the NetCDF for LIS simulation?

[dmocko]

Yes, please use the current master branch.

Just go to this site: https://github.com/NASA-LIS/LISF

Ensure you are in the "master" branch (seen on the left).

Click on the green "Code" button on the right to download the code.

This code contains the code to run the NLDAS-2 netCDF data.

[shaider2]

Hi,
Thank you so much again. I have downloaded the code from master branch and compiled it. It is recognizing the format. However, I am getting a different error now. I have used the previous config file. I have attached the new log file for you to look over. I will really appreciate if you can give some suggestions for this.
lislog_12km.0000 (2).txt

[dmocko]

Please see the LIS Users' Guide: https://nasa-lis.github.io/LISF/LIS_users_guide/LIS_users_guide.html

Replace the old "NLDAS2" config entries with the above. And be sure to point to the correct directory.

You probably do not need to use the "FORB" forcing. If you don't use it, only the first new config entry is needed in your lis.config:

NLDAS-2.0 FORA forcing directory:

[shaider2]

Hi, Thank you so much again. I have edited as per instructions and have attached a screenshot for that particular section. It will be great if you can let me know if it works. Thank you so much again. Kind Regards, Syeda Tasneem Binta Haider

…

________________________________ From: David Mocko ***@***.***> Sent: Friday, April 25, 2025 3:26 PM To: NASA-LIS/LISF ***@***.***> Cc: Syeda Tasneem Binta Haider ***@***.***>; Mention ***@***.***> Subject: Re: [NASA-LIS/LISF] Using netcdf data for metforcing (Discussion #1703) Caution: Non-NU Email Please see the LIS Users' Guide: https://nasa-lis.github.io/LISF/LIS_users_guide/LIS_users_guide.html<https://urldefense.com/v3/__https://nasa-lis.github.io/LISF/LIS_users_guide/LIS_users_guide.html__;!!PvXuogZ4sRB2p-tU!HbGNlgGdJ-DUdXM68qPJ2wn9ILVPnfF3CQ79z8AedN4K0Oxus0wJfVXTsEHDTRnA_eBgHOFVvUalPzeAhH5ZyN64Ah5mMA$> Screenshot.2025-04-25.at.4.23.47.PM.png (view on web)<https://urldefense.com/v3/__https://github.com/user-attachments/assets/3887f96c-8d5f-4d2f-9a67-8f4e329305f3__;!!PvXuogZ4sRB2p-tU!HbGNlgGdJ-DUdXM68qPJ2wn9ILVPnfF3CQ79z8AedN4K0Oxus0wJfVXTsEHDTRnA_eBgHOFVvUalPzeAhH5ZyN7e-m79vg$> Replace the old "NLDAS2" config entries with the above. And be sure to point to the correct directory. You probably do not need to use the "FORB" forcing. If you don't use it, only the first new config entry is needed in your lis.config: NLDAS-2.0 FORA forcing directory: — Reply to this email directly, view it on GitHub<https://urldefense.com/v3/__https://github.com/NASA-LIS/LISF/discussions/1703*discussioncomment-12951039__;Iw!!PvXuogZ4sRB2p-tU!HbGNlgGdJ-DUdXM68qPJ2wn9ILVPnfF3CQ79z8AedN4K0Oxus0wJfVXTsEHDTRnA_eBgHOFVvUalPzeAhH5ZyN4tOtvqGg$>, or unsubscribe<https://urldefense.com/v3/__https://github.com/notifications/unsubscribe-auth/A3J6JHFB3J4E3SJKTJPWVTT23KLAPAVCNFSM6AAAAAB34BX5ICVHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTEOJVGEYDGOI__;!!PvXuogZ4sRB2p-tU!HbGNlgGdJ-DUdXM68qPJ2wn9ILVPnfF3CQ79z8AedN4K0Oxus0wJfVXTsEHDTRnA_eBgHOFVvUalPzeAhH5ZyN6sTtnRBg$>. You are receiving this because you were mentioned.Message ID: ***@***.***>

[dmocko]

The screenshot that I see is only three dogs (EDIT: "dots" not "dogs") with a line underneath. I can't tell if it's working for you or not.

My lislog file that's working looks like this (and continues on):

 [INFO] getting file1a.. 
 ./INPUT/NLDAS2.FORCING/2017/001/NLDAS_FORA0125_H.A20170101.0000.020.nc
 [INFO] getting file2a.. 
 ./INPUT/NLDAS2.FORCING/2017/001/NLDAS_FORA0125_H.A20170101.0100.020.nc
[INFO] LIS cycle time: 01/01/2017 00:30:00
[INFO] LIS cycle time: 01/01/2017 00:45:00
[INFO] LIS cycle time: 01/01/2017 01:00:00
 [INFO] getting file2a.. 
 ./INPUT/NLDAS2.FORCING/2017/001/NLDAS_FORA0125_H.A20170101.0200.020.nc
[INFO] LIS cycle time: 01/01/2017 01:15:00
[INFO] LIS cycle time: 01/01/2017 01:30:00

[shaider2]

Hi @dmocko ,
I'm sorry for the inconvenience in the last message. I have uploaded the configuration file I used. And the simulation was completed successfully this time. I can't thank you enough for all the support you provided.
lis.config.coldstart (3).txt

[dmocko]

Thanks to you as well, as it became clear that we need to put out a public release with the updated code, and to update the public walkthrough testcase. We're working on it and hope to have it released soon.

[shaider2]

Hi @dmocko ,
That will be a great initiative.
However, I have encountered a new issue. I am running LIS for a 3 year long simulation. The output files are organized in the monthly folder. However, in the output files, LIS_HIST files are not available. The model is only simulating the LIS_RST files. I will really appreciate any feedback regarding this issue.

[shaider2]

Hi @dmocko ,
Please ignore my previous message. The simulation is going fine. The restart files are for 1st 3 years. It has the output for the last year