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
Hi!
We were able to run a point and a tile using pSIMS with DSSAT v 4.8. Now we would like to move to running pSIMS via swift. We added a new site "testsite" to the conf/swift.properties and installed swift-t, which is a newer version of swift-095. However, swift -site testsite -resume $( ls -1t psims-all*.rlog | head -1 ) psims-all.swift -campaign=/p/projects/agrica/pSIMS_py3/pSIMS/test_run_DSSAT/run012/campaign -param=/p/projects/agrica/pSIMS_py3/pSIMS/test_run_DSSAT/run012/params.psims -cwd=/p/projects/agrica/pSIMS_py3/pSIMS/test_run_DSSAT/run012 -num_chunks=1 -variables=PDAT,ADAT,MDAT,HWAM,IRCM,TMAXA,TMINA,PRCP,CO2A,SRADA -cal_vars= -split=1 2>&1 | tee -a swift.out echo | tee -a swift.out
throws the following error message. Could not read: testsite
It seems that the command "site" is unknown to swift-t. Did anyone experience this issue and has a solution?
The text was updated successfully, but these errors were encountered:
Hi!
We were able to run a point and a tile using pSIMS with DSSAT v 4.8. Now we would like to move to running pSIMS via swift. We added a new site "testsite" to the conf/swift.properties and installed swift-t, which is a newer version of swift-095. However,
swift -site testsite -resume $( ls -1t psims-all*.rlog | head -1 ) psims-all.swift -campaign=/p/projects/agrica/pSIMS_py3/pSIMS/test_run_DSSAT/run012/campaign -param=/p/projects/agrica/pSIMS_py3/pSIMS/test_run_DSSAT/run012/params.psims -cwd=/p/projects/agrica/pSIMS_py3/pSIMS/test_run_DSSAT/run012 -num_chunks=1 -variables=PDAT,ADAT,MDAT,HWAM,IRCM,TMAXA,TMINA,PRCP,CO2A,SRADA -cal_vars= -split=1 2>&1 | tee -a swift.out echo | tee -a swift.out
throws the following error message.
Could not read: testsite
It seems that the command "site" is unknown to swift-t. Did anyone experience this issue and has a solution?
The text was updated successfully, but these errors were encountered: