BrownDog/NARR sipnet.clim files not being generated correctly #2048
Comments
|
Interestingly the created driver shows up as an option if you go back to the same site/model combo
|
|
Also, not sure if this is what is supposed to happen but a sipnet.clim folder was created in the top-level of the pecan workflow folder as seen here: But the folder is empty |
|
Here is what a run folder looks like: |
|
Based on a comment by @robkooper on Slack, it looks like the returned file is a .zip file without the correct extension. If I rename the file I can successfully extract the data file which is a properly formatted sipnet.clim file. |
|
Ran it again and see that now there are two different BD clim files in the improperly named .zip file Another issue is that the sym link used in job.sh doesnt match the file names: |
|
A quick check of what I think should be the way it is setup: |
|
@robkooper any chance you have had time to look into the BD issues with NARR? |
|
I think this might have been fixed with #2039 I will need to test this. |
|
which year are you selecting? |
|
@robkooper just tried again, and got this: Here is the directory, which actually looks better this time: But nothing in the file?? From the workflow.log |
|
Here is my run info |
|
I believe this is fixed on the develop branch but not deployed yet. I will work with @yan130 to test and see if it works on the dev server with that specific file. |
|
@robkooper OK thanks. I am using develop branch for these runs, just not yet pushed the changes for a local branch? |
|
we don't have the develop branch deployed here. this particular instance is following the master branch. I was hoping to deploy the new release there. I'll check with @tonygardella when the new release will happen. |
|
@robkooper I'm not sure I follow......I am also still not certain which end this bug is on. I assume we will make sure it can work for both master and dev? |
|
Do we have any fixes for this yet? @para2x at some point in your multi-site SDA, I think we are going to want to run with NARR drivers across sites, or at least that was the original plan. But we have been waiting for a fix. |
|
Bump. Has anyone else been able to use BrownDog NARR with sipnet lately? If so please let me know, perhaps it has been addressed and is working again....unclear. |
|
If there are issues with BrownDog NARR, I'd use the THREDDS-based NARR_site in the interim |
|
@robkooper I test that case on prod and the error is a wrong ftp link:
remotefunc <- function() {PEcAn.data.atmosphere::download.NARR(site_id='1135', lat.in=40.6658, lon.in=-77.9041, model=NULL, scenario=NULL, ensemble_member=NULL, overwrite=FALSE, outfolder='/home/polyglot/cache/PEcAn/NARR_site_1-25731/', start_date='1990-01-01', end_date='2014-12-31')} Attaching package: ‘PEcAn.utils’ The following object is masked from ‘package:utils’: 2019-01-23 11:18:33 DEBUG [PEcAn.data.atmosphere::download.NARR] : PS: I don't know why it download from 2014, I just set start as 1990 and end as 1991. |
|
Welcome to government shutdown maybe? |
|
@yan130 I just tested that FTP link and it looks to be back up |
|
I just ran this and it seems to be pulling down data |
|
@serbinsh I running it, takes some time ( maybe a day), I will update you when it is done or get error. |
|
Thanks @yan130 Are you testing the basic NARR code or the BrownDog version? |
|
I need to run basic NARR code on BrownDog server first. |
|
Ah, ok that makes sense. thank you! |
|
Strange, I updated pecan to latest dev and now get this error: Yet the similar command above is still working, need to sort out why there is a difference now |
|
Aha, the issue with the newer command in PEcAn is that it sets "method" to NULL by default, which errors for me. But if I run as: it runs fine. |
|
I cannot find in here: https://github.com/PecanProject/pecan/blob/develop/modules/data.atmosphere/R/download.NARR.R OR here: https://github.com/PecanProject/pecan/blob/develop/modules/data.atmosphere/R/download.NARR_site.R where "method" is getting set to NULL by default? Its also not happening in here, as far as I can tell? https://github.com/PecanProject/pecan/blob/develop/web/03a-narr.php . But that "method=NULL, " is breaking NARR for me on modex because that needs to be grabbed from our R profile. |
|
current error log: Begin Model Specific Conversion |
|
@yan130 I get this error message on my end: |
this can be fixed by adding new api url: to all geonames::GNtimezone calls. @robkooper @serbinsh it should be working now, please leave a comment if you still have problems. |
|
Check what version of geonames is installed. This might be fixed in an update. |
|
latest one, no update since 2014. |
|
Can you try |
|
not working. didn't find the hostname in source code of 'ropensci/geonames' |
|
Just following up on this, any progress on getting the NARR process to run again via BD? |
|
I just tried again this AM and found that it does create a sipnet.clim file, BUT its empty |
|
This issue is stale because it has been open 365 days with no activity. |
Describe the bug
related to #2047
I am attempting to generate NARR drivers for sipnet at two different sites and am running into an issue where the output of the BD command is either an empty file or gibberish. For example:
That is an example file from WF https://modex.bnl.gov/pecan_dev/05-running.php?workflowid=2000000991 where I was running at AF site Susquehanna Shale Hills Critical Zone Observatory (US-SSH)
To Reproduce
Steps to reproduce the behavior:
, US
Expected behavior
Appropriate NARR driver is created and model ensemble runs complete successfully
Screenshots
none
Machine (please complete the following information):
Additional context
none
The text was updated successfully, but these errors were encountered: