You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This means that if you have two models, most methods must be compiled twice due to the type of Dual numbers changing due to the changing tag. I don't see a reason why the tag could not be defined inside ModelBaseEcon itself and then shared among the models. The reason for having the tag at all is to prevent "perturbation confusion" (JuliaDiff/ForwardDiff.jl#83) but that doesn't seem (at least to me) to apply here.
As it is right now, each model gets it's own
ForwardDiff
tag:ModelBaseEcon.jl/src/evaluation.jl
Line 149 in 7a7dfa8
This means that if you have two models, most methods must be compiled twice due to the type of
Dual
numbers changing due to the changing tag. I don't see a reason why the tag could not be defined inside ModelBaseEcon itself and then shared among the models. The reason for having the tag at all is to prevent "perturbation confusion" (JuliaDiff/ForwardDiff.jl#83) but that doesn't seem (at least to me) to apply here.That would mean that all the precompile stuff at
ModelBaseEcon.jl/src/evaluation.jl
Lines 22 to 54 in 7a7dfa8
could instead be compiled into ModelBaseEcon (for values of
N
from 1 to the max chunk size) instead of for each model.The text was updated successfully, but these errors were encountered: