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
function.value doesn't update its value field even after input pool is connected to function (which should be nOut of pool, which is nInit?)
2.un-setting the solver on the model, doesn't un-zombify the function object when connected to reaction, its is still zombiefunction
(This is bcos while unsettling the solver a check on function is make to see if it has a message of 'setN' and not setNumKf eg file attached is funtionzombie.txt
one can see when function connected to pool, unzombify but not when connected to reaction )
3.when function connected to reaction via setNumKf, the numKf or Kf values is not updated but the value is set.
Also one to see whether setting numKb is allowed or not.
(Vinu said that setNumKb is not allowed via moose.connect, but directly one can set "numKb" on reaction and value is updated.)
All these are confusing to the user as these are not documented or need to be updated. funtionreaction.txt
hrani
changed the title
function.value not updated, either reaction rate's value get updated after function setting setNumKf
KnowIssue: function.value not updated, either reaction rate's value get updated after function setting setNumKf
Apr 15, 2020
I have upload a sample file.
Few concern
2.un-setting the solver on the model, doesn't un-zombify the function object when connected to reaction, its is still zombiefunction
(This is bcos while unsettling the solver a check on function is make to see if it has a message of 'setN' and not setNumKf eg file attached is funtionzombie.txt
one can see when function connected to pool, unzombify but not when connected to reaction )
3.when function connected to reaction via setNumKf, the numKf or Kf values is not updated but the value is set.
(Vinu said that setNumKb is not allowed via moose.connect, but directly one can set "numKb" on reaction and value is updated.)
All these are confusing to the user as these are not documented or need to be updated.
funtionreaction.txt
partly mentioned
The text was updated successfully, but these errors were encountered: