Closed SOLV-Code closed 3 years ago
Have been using 3 names interchangeably: "mechanistic", "return Rate", and "rate".
In the package functions and app we need to avoid confusion and messiness, so have to pick one.
I'm currently implementing "rate", just because that's what I used in the code of the estimation function.
Not a big deal to change, though.
So, just need a team decision, and then stick to it :-)
Executive decision: call it ReturnRate
Done
Have been using 3 names interchangeably: "mechanistic", "return Rate", and "rate".
In the package functions and app we need to avoid confusion and messiness, so have to pick one.
I'm currently implementing "rate", just because that's what I used in the code of the estimation function.
Not a big deal to change, though.
So, just need a team decision, and then stick to it :-)