Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Meta-analysis AUTO broken ... again #1217

Closed
mdietze opened this issue Dec 1, 2016 · 3 comments · Fixed by #2358
Closed

Meta-analysis AUTO broken ... again #1217

mdietze opened this issue Dec 1, 2016 · 3 comments · Fixed by #2358

Comments

@mdietze
Copy link
Member

mdietze commented Dec 1, 2016

Meta-analysis seems to be running for every run again. Need to add debugging this so it only runs when needed back on the list. I'm seriously tempted to just remove the MA block from the default run specification so that users have to turn it on during advanced edit.

@tonygardella
Copy link
Contributor

Taking out the meta-anlysis tags in the pecan.xml skipped that step but made write.configs fail:

2017-07-10 10:46:38 INFO   [get.parameter.samples] : 
   Selected PFT(s): populus 
Warning in rm(prior.distns, post.distns, trait.mcmc) :
  object 'prior.distns' not found
Warning in rm(prior.distns, post.distns, trait.mcmc) :
  object 'post.distns' not found
Warning in rm(prior.distns, post.distns, trait.mcmc) :
  object 'trait.mcmc' not found
Warning in readChar(con, 5L, useBytes = TRUE) :
  cannot open compressed file '/home/carya/output//PEcAn_99000000001/pft/populus/prior.distns.Rdata', probable reason 'No such file or directory'
Error in readChar(con, 5L, useBytes = TRUE) : cannot open the connection

Looks like none of the prior data or parameter info was saved to the pft directory. Next step is to look into why none of the trait data was generated without the meta analysis.

@mdietze
Copy link
Member Author

mdietze commented Jul 10, 2017

Well, if we don't run the MA we don't need to run the trait query either, but we do need to query to get the latest posteriors. They would no longer be in the PFT directory of that run, but in the directory of the run when the MA was updated.

@tonygardella tonygardella moved this from Suggested, unconfirmed to Selected for sprint in PEcAn bugfix sprint: DUE Sep 15th. Aug 14, 2017
@tonygardella tonygardella moved this from Selected for sprint to Assigned in PEcAn bugfix sprint: DUE Sep 15th. Aug 14, 2017
@tonygardella tonygardella moved this from Assigned to In progress in PEcAn bugfix sprint: DUE Sep 15th. Aug 28, 2017
@tonygardella tonygardella modified the milestones: 1.5.1, On Deck Sep 7, 2017
@tonygardella tonygardella modified the milestones: 1.5.1, On Deck Sep 28, 2017
@ashiklom
Copy link
Member

Bump!

So I think I may have made some progress on this: get.trait.data, which I think is responsible for figuring out whether or not to run the meta analysis, looks for the trait.data.Rdata, prior.distns.Rdata, and either species.csv or cultivar.csv. However, these files don't come up in the dbfile.check (nor, for that matter, does post.distns.Rdata because it's a symlink, but the file it points to -- post.distns.MA.Rdata -- does come up), so I think there is a problem with how they are registered somewhere. I'll keep digging...

files <- dbfile.check(type = 'Posterior', container.id = pft$posteriorid, con = dbcon)
ids <- match(c('trait.data.Rdata', 'prior.distns.Rdata', pft_member_filename), files$file_name)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
No open projects
Development

Successfully merging a pull request may close this issue.

3 participants