-
Notifications
You must be signed in to change notification settings - Fork 35
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
SS_readdat_3.30 #140
Comments
I'm sure the
|
Probably had `agebin_vector` in their workspace while they were testing it.
I have done similar things in the past many times. Always a good practice
to close `R` and test everything in a new session before committing.
…On Thu, Apr 6, 2017 at 1:10 PM, Ian Taylor ***@***.***> wrote:
I'm sure the d$ was just forgotten. Thanks for catching this.
SS_readdat_3.30 was developed by @cgrandin <https://github.com/cgrandin>
who kindly took on the task by modifying SS_readdat_3.24. However, I'm
sure it hasn't been tested on, and probably doesn't work for, any model
that uses the generalized size frequency data option which is where
sizefreq_bins_list comes in. I'm not sure how it worked for a model that
used age data for which agebin_vector would have played a role.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#140 (comment)>, or mute
the thread
<https://github.com/notifications/unsubscribe-auth/AD6xFEnrAnMqfLIEWfO4BklT0V7lnDyuks5rtUargaJpZM4M2FY7>
.
--
Kelli Faye Johnson
kellifayejohnson@gmail.com
|
Ian is correct, I missed the d$. I only tested for the options used in the hake assessment, and just pasted the rest in for convenience (we were short on time). Thanks for fixing it. |
Closing old issue that was sorted out some time ago. |
There are two objects,
agebin_vector
andsizefreq_bins_list
, that have no visible binding inSS_readdat_3.30
. Both of these are referenced prior to their use without binding as being part of the objectd
. Did thed$
just forget to be carried over to subsequent lines?The text was updated successfully, but these errors were encountered: