Skip to content
GitLab
Projects Groups Topics Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
  • Sign in
  • S s2dverification
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributor statistics
    • Graph
    • Compare revisions
  • Issues 65
    • Issues 65
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 7
    • Merge requests 7
  • Deployments
    • Deployments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • Repository
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Commits
  • Issue Boards
Collapse sidebar
  • Earth SciencesEarth Sciences
  • s2dverification
  • Issues
  • #29
Closed
Open
Issue created Mar 06, 2015 by Chloé Prodhomme@cprodhommeDeveloper

probleme when loading one leadtime only with the new Load

Hi,

When I try these script with new Load

  meantemp=Load("tas", c("b0cm","b0gq"), obs = "ERAint",
    sdates=c("19900501"), nleadtime = 4, nmember = 10, leadtimemin = 1,
    leadtimemax = 1, storefreq = "monthly", sampleperiod = 1,
    method = "conservative", output="areave")

I get the following error message

Error in checkForRemoteErrors(val) : 
  2 nodes produced errors; first error: missing value where TRUE/FALSE needed

While this one (which select 2 lead times instead of one) works fine:

  meantemp=Load("tas", c("b0cm","b0gq"), obs = "ERAint",
    sdates=c("19900501"), nleadtime = 4, nmember = 10, leadtimemin = 1,
    leadtimemax = 2, storefreq = "monthly", sampleperiod = 1,
    method = "conservative", output="areave")

I have also tried different experiments, different start dates, different variable, different lead time values and different type of output (lonlat and areave) and the results remains the same: it does not work with one leadtime and it works with two or more.

@nmanubens could you pease have look? PS: people who might be interested in this issue: @vguemas @eexarchou @mmenegoz @fmassonnet @lpcaron @obellprat @vtorralba @nevensf @ngonzalez

Assignee
Assign to
Time tracking