warn user about NAs in RHS only nodes at model building time about nimble HOT 6 CLOSED

I agree it is unclear what is needed here since it is legitimate to define (and compile) a model before putting values into it. Maybe we should provide a nimbleFunction that checks if a model is ready to use, so it would be easy to insert that step at the beginning of other nimbleFunctions when needed?

from nimble.

Maybe we should provide a nimbleFunction that checks if a model is ready
to use, so it would be easy to insert that step at the beginning of other
nimbleFunctions when needed?

The function described above is more or less exactly the nimbleFunction I
wrote called "initializeModel", which is already in use at the beginning of
algorithmic nimbleFunctions in devel.

Daniel

On Mon, May 4, 2015 at 4:01 PM, perrydv [email protected] wrote:

I agree it is unclear what is needed here since it is legitimate to define
(and compile) a model before putting values into it. Maybe we should
provide a nimbleFunction that checks if a model is ready to use, so it
would be easy to insert that step at the beginning of other nimbleFunctions
when needed?

—
Reply to this email directly or view it on GitHub
#13 (comment).

from nimble.

should we
a) call initializeModel() at the end of nimbleModel()
b) mention initializeModel() in the manual?

If we do do (a), I don't think we want to automatically simulate into
stochastic nodes unless a user specifically requests it, but deterministic
nodes are another story.

I think the main things to be concerned about are missing values in data
nodes, stochastic parameter nodes, and RHS only nodes, in terms of what to
warn users about.

On Tue, May 26, 2015 at 1:17 PM, Daniel Turek [email protected]
wrote:

Maybe we should provide a nimbleFunction that checks if a model is ready
to use, so it would be easy to insert that step at the beginning of other
nimbleFunctions when needed?

The function described above is more or less exactly the nimbleFunction I
wrote called "initializeModel", which is already in use at the beginning of
algorithmic nimbleFunctions in devel.

Daniel

On Mon, May 4, 2015 at 4:01 PM, perrydv [email protected] wrote:

I agree it is unclear what is needed here since it is legitimate to
define
(and compile) a model before putting values into it. Maybe we should
provide a nimbleFunction that checks if a model is ready to use, so it
would be easy to insert that step at the beginning of other
nimbleFunctions
when needed?

—
Reply to this email directly or view it on GitHub
#13 (comment).

—
Reply to this email directly or view it on GitHub
#13 (comment).

from nimble.

I had already added a very brief section on initializeModel() to the
developer manual. It's at the very end.

We could add an option to initializeModel() which determines whether or not
it simulates into missing-valued nodes. At the moment it does.

Daniel

On Tue, May 26, 2015 at 1:48 PM, Christopher Paciorek <
[email protected]> wrote:

should we
a) call initializeModel() at the end of nimbleModel()
b) mention initializeModel() in the manual?

If we do do (a), I don't think we want to automatically simulate into
stochastic nodes unless a user specifically requests it, but deterministic
nodes are another story.

I think the main things to be concerned about are missing values in data
nodes, stochastic parameter nodes, and RHS only nodes, in terms of what to
warn users about.

On Tue, May 26, 2015 at 1:17 PM, Daniel Turek [email protected]
wrote:

Maybe we should provide a nimbleFunction that checks if a model is
ready
to use, so it would be easy to insert that step at the beginning of other
nimbleFunctions when needed?

The function described above is more or less exactly the nimbleFunction I
wrote called "initializeModel", which is already in use at the beginning
of
algorithmic nimbleFunctions in devel.

Daniel

On Mon, May 4, 2015 at 4:01 PM, perrydv [email protected]
wrote:

I agree it is unclear what is needed here since it is legitimate to
define
(and compile) a model before putting values into it. Maybe we should
provide a nimbleFunction that checks if a model is ready to use, so it
would be easy to insert that step at the beginning of other
nimbleFunctions
when needed?

—
Reply to this email directly or view it on GitHub
<#13 (comment)
.

—
Reply to this email directly or view it on GitHub
#13 (comment).

—
Reply to this email directly or view it on GitHub
#13 (comment).

from nimble.

My thought is that at the end of nimbleModel(), we:

1. simulate into all deterministic nodes
2. warn users of any data nodes, RHS only nodes, or stochastic param nodes
   that are NA or NaN

We could have a flag to nimbleModel that turns off warnings or have a new
nimbleOption that controls that and other warnings.

For the purpose of #1, having an option for initializeModel that would
avoid simulating stoch nodes would be good.

On Tue, May 26, 2015 at 3:25 PM, Daniel Turek [email protected]
wrote:

I had already added a very brief section on initializeModel() to the
developer manual. It's at the very end.

We could add an option to initializeModel() which determines whether or not
it simulates into missing-valued nodes. At the moment it does.

Daniel

On Tue, May 26, 2015 at 1:48 PM, Christopher Paciorek <
[email protected]> wrote:

should we
a) call initializeModel() at the end of nimbleModel()
b) mention initializeModel() in the manual?

If we do do (a), I don't think we want to automatically simulate into
stochastic nodes unless a user specifically requests it, but
deterministic
nodes are another story.

I think the main things to be concerned about are missing values in data
nodes, stochastic parameter nodes, and RHS only nodes, in terms of what
to
warn users about.

On Tue, May 26, 2015 at 1:17 PM, Daniel Turek [email protected]
wrote:

Maybe we should provide a nimbleFunction that checks if a model is
ready
to use, so it would be easy to insert that step at the beginning of
other
nimbleFunctions when needed?

The function described above is more or less exactly the
nimbleFunction I
wrote called "initializeModel", which is already in use at the
beginning
of
algorithmic nimbleFunctions in devel.

Daniel

On Mon, May 4, 2015 at 4:01 PM, perrydv [email protected]
wrote:

I agree it is unclear what is needed here since it is legitimate to
define
(and compile) a model before putting values into it. Maybe we should
provide a nimbleFunction that checks if a model is ready to use, so
it
would be easy to insert that step at the beginning of other
nimbleFunctions
when needed?

—
Reply to this email directly or view it on GitHub
<
#13 (comment)
.

—
Reply to this email directly or view it on GitHub
<#13 (comment)
.

—
Reply to this email directly or view it on GitHub
#13 (comment).

—
Reply to this email directly or view it on GitHub
#13 (comment).

from nimble.

I believe this is addressed with our new check() functionality.

from nimble.