Issue reading ISMN data into LVT #1685
-
Hello All! I'm running into some trouble reading ISMN data into LVT 7.5.4. I am running LVT with LIS output as the first datastream and ISMN as the second, and trying to compare soil moisture between the two. Based on my output data, it looks like LVT is reading in the LIS Output data, but not the ISMN data. I have anom, mean, stdev, and variance output for the LIS Output (datastream 1), but null for ISMN (datastream 2). The acorr, armse, bias, mae, rmse, and ubrmse are all missing values because they require both datastream 1 and 2 to be calculated. However, in the logfile it looks like each ISMN file is being read in. Has anyone experienced a similar issue before? I have included my lvt.config information below and attached logfile and an example output file for reference. LVT running mode: "Data intercomparison" Start mode: coldstart #LIS domain Input domain and mask data file: ./LDTOUT/lis_input.10km_noahmp.nc LVT datastream attributes table:: LVT surface soil layer thickness: 0.10 #stats specifications (only applicable to retrospective mode) ISMN observation directory: ../ISMN_limited LIS output analysis data class: "LSM" |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment
-
Hi @alexamarco Yes, I think we have experienced this before. See the last comment on this Issue: #248 Try changing this in your lvt.config file:
Then in your running LVT directory, make a symbolic link to the data:
Then try to run LVT again, and let us know if it does or does not work. Apologies for the trouble - I haven't been able to pin down when/why this happens only sometimes. |
Beta Was this translation helpful? Give feedback.
Hi @alexamarco
Yes, I think we have experienced this before. See the last comment on this Issue: #248
Try changing this in your lvt.config file:
ISMN observation directory: ./v2
Then in your running LVT directory, make a symbolic link to the data:
ln -s ../ISMN_limited v2
Then try to run LVT again, and let us know if it does or does not work.
Apologies for the trouble - I haven't been able to pin down when/why this happens only sometimes.