Closed dill closed 8 years ago
We have vignettes and examples (specifically spotted dolphins) already up and running with Distance. The answer to this depends upon how much of a high-wire act the workshop is to be.
I take your point about having lots of beta-testers at a workshop, the other side of the coin is having something that is bullet-proof at a workshop. Considering the number of bodies (you) that will be at the workshop, how much fire-fighting do you want to do?
Provided we can ensure that the knitr(?) exercises all run (and have been tested to run on as many platforms as possible), I think the additional stress is worth it to potentially expose unusual bugs in a setting where I can see what's directly going on.
I'm likely to have a very different opinion on day 2 of the workshop.
On 01/05/2015 03:32, erex wrote:
We have vignettes and examples (specifically spotted dolphins) already up and running with Distance. The answer to this depends upon how much of a high-wire act the workshop is to be.
I take your point about having lots of beta-testers at a workshop, the other side of the coin is having something that is bullet-proof at a workshop. Considering the number of bodies (you) that will be at the workshop, how much fire-fighting do you want to do?
— Reply to this email directly or view it on GitHub https://github.com/DistanceDevelopment/spatial-workshops/issues/7#issuecomment-98066325.
Due to time constraints I'm going to go for Distance
over Distance2
.
Relating to #6 somewhat, are we to teach
Distance
orDistance2
. I don't think there is too much of a disadvantage of teaching the latter as it'll make for a good test of the software and will hopefully "do" MRDS by then (if it doesn't, it will at some point, where asDistance
never will).My plan is to have
dsm
be able to talk to both packages anyway.