Repository navigation
remove uses of the nimble namespace, as we move towards nimble2 - #63
Conversation
|
Ok I did some work to address some of the test failures. This was done with a bit of duct tape and chewing gum to get things working in terms of transitioning to There are still some modelValues test failures plus a failure with |
|
Evidently the |
|
yeah I think nimbleModel makes sense as a home for it. I suppose one could argue that various distributions could be used in nFunction code and maybe it should be in nCompiler, but if we think of it as a "user-provided" distribution where the "user" is nimbleModel/us, then nimbleModel makes sense. |
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
|
@paciorek This branch is now passing tests. I ended up keeping the feature from I am happy with this branch now, if you want to review it. |
|
Looks good. One thing was that on quick glance it looked like the parameterization for dexp_nComp differs from dexp_nimble? So you will merge this and then do the styler pass? |
|
Can you say what you mean? Both are |
|
I will go ahead with the merge and then the |
I am not sure if this is ready to merge, but let's see if it passes testing and any input from @paciorek.
This simply comments-out the use of
nf_changeNimKeywords, pending discussion of where that should be done. (See #60).I think
calc_dmnormAltParamsandcalc_dwishAltParamswill both work asnCompiler::nFunction. However full testing will really come from uses innimble2.