As of current, the initial conditions of all nodes are set to 0.5 by default (following the merging from CNORode2017 repository). This assumption doesn't apply for all the cases so users should have an option to assign the initial condition (ideally both for all nodes and for each specific node).
One circumvent solution around this issue is to add the initial condition of each node at time 0 in the MIDAS file while setting the measurements of the non-measured value as NA (so that they won't be accounted in the fitting). However, this is a highly non-optimal solution so a dedicated modification of the function(s) is needed to resolve this issue.
As of current, the initial conditions of all nodes are set to 0.5 by default (following the merging from CNORode2017 repository). This assumption doesn't apply for all the cases so users should have an option to assign the initial condition (ideally both for all nodes and for each specific node).
One circumvent solution around this issue is to add the initial condition of each node at time 0 in the MIDAS file while setting the measurements of the non-measured value as NA (so that they won't be accounted in the fitting). However, this is a highly non-optimal solution so a dedicated modification of the function(s) is needed to resolve this issue.