[kepler-dev] [Bug 3266] - ENM/GARP_MultipleSpecies-V.xml problems

bugzilla-daemon at ecoinformatics.org bugzilla-daemon at ecoinformatics.org
Thu May 8 13:35:08 PDT 2008


berkley at nceas.ucsb.edu changed:

           What    |Removed                     |Added
           Severity|normal                      |major

------- Comment #10 from berkley at nceas.ucsb.edu  2008-05-08 13:35 -------
This complex workflow depends on a lot of external dependencies.  If any one of
them fail, the workflow fails.  I've been playing with it all day trying to
narrow down what we could do to make it more stable.  short of redesigning it
to run only in java and not using external file sources, I'm not sure there is
anything we can do.  90% of the time on windows and OSX, it runs fine.  Why it
chooses to fail sometimes, I'm not completely sure.  I've played with filename
variables, R script working directories, file sources, etc.  Everytime I think
it's fixed, it eventually will lock up, crash or somehow break.  

My thinking on this right now is we should not hold up the kepler release
because of this (and the other GARP-SingleSpecies_BestRuleSet) workflow.  I'm
aware that GARP is a key part of SEEK and I would really like it to work
flawlessly, but at this point, I don't think it's going to without a lot of
work.  I move to push these bugs to 1.1 and release Kepler as it is.  We could
add a caveat to the GARP workflows letting people know we know about problems
and giving some basic solutions.  I think if we try to solve all of these
problems with GARP, Kepler is not going to be released for at least a month or
probably more.  

Any comments?  Please say whether you think the GARP workflows working
perfectly should be a pre-requisite for releasing kepler.  I've marked this as
"major" so that it stands out in the search results until we resolve this.

More information about the Kepler-dev mailing list