You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
The writing of a fileX does not follow the strict formatting rules for DSSAT data input. I am looking for guidance on how to best update the package to address this issue.
To Reproduce
Steps to reproduce the behavior:
Minimalistic example (the shortest complete code that causes the mistake)
Read the fileX and get the emergence data.
from tradssat.exper import exper_file
mzx_file = exper_file.ExpFile("../data/Maize/IUAF9901.MZX")
mzx_file.get_value("EDATE")
Write a new fileX with the updated emergence date. mzx_file.write("../data/Maize_Iowa_tradssat/IUAF9901.MZX")
Version of traDSSAT (tradssat.__version__) and operating system (Linux, Windows, Mac, ...)
traDSSAT version is 0.1.5
My OS is MacOS Catalina Version 10.15.7
A copy of any DSSAT input file(s) involved
Expected behavior
The newly written .MZX file does not match the one that is provided by DSSAT. The formatting is off. (I have provided a few screen shots to illustrate this where the left one shows the original MZX and the file on the right shows the one that is re-written with tradssat.) As a result, the DSSAT software cannot read the newly written file correctly, and a simulation is terminated.
Additional context
I performed a similar exercise for a .WTH file, and I was successfully able to use the newly written .WTH in a DSSAT simulation.
I attached the original .MZX file (saving it as a .txt file bc github doesn't allow me to upload a .mzx file) GHWA0401.txt
Below, I show the warning and error outputs from the DSSAT simulation. Somehow, it is having trouble recognizing the FIELD section.
The text was updated successfully, but these errors were encountered:
Describe the bug
The writing of a fileX does not follow the strict formatting rules for DSSAT data input. I am looking for guidance on how to best update the package to address this issue.
To Reproduce
Steps to reproduce the behavior:
> array([-99, -99, -99, -99])
> array([99154, 99154, 99154, 99154])
mzx_file.write("../data/Maize_Iowa_tradssat/IUAF9901.MZX")
tradssat.__version__
) and operating system (Linux, Windows, Mac, ...)Expected behavior
The newly written .MZX file does not match the one that is provided by DSSAT. The formatting is off. (I have provided a few screen shots to illustrate this where the left one shows the original MZX and the file on the right shows the one that is re-written with tradssat.) As a result, the DSSAT software cannot read the newly written file correctly, and a simulation is terminated.
Additional context
I performed a similar exercise for a .WTH file, and I was successfully able to use the newly written .WTH in a DSSAT simulation.
I attached the original .MZX file (saving it as a .txt file bc github doesn't allow me to upload a .mzx file)
GHWA0401.txt
Below, I show the warning and error outputs from the DSSAT simulation. Somehow, it is having trouble recognizing the FIELD section.
The text was updated successfully, but these errors were encountered: