Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

SetNumKf disables Kb #408

Open
vinuvargheseijk opened this issue Apr 13, 2020 · 5 comments
Open

SetNumKf disables Kb #408

vinuvargheseijk opened this issue Apr 13, 2020 · 5 comments
Assignees

Comments

@vinuvargheseijk
Copy link

vinuvargheseijk commented Apr 13, 2020

I think that using setNumKf will disable the Kb for the reaction. For example, using the example https://moose.ncbs.res.in/readthedocs/user/py/rdesigneur/rdes.html#controlling-a-reaction-by-a-function change the reac.Kb to any value. The reults won't change.

Please refer to my lab note for example.
https://labnotes.ncbs.res.in/bhalla/setnumkf-disables-kb-reac

@dilawar
Copy link
Contributor

dilawar commented Apr 14, 2020

I also used numKf everywhere in my CaMKII model with moose.Function. I guess the trouble is that during simulation, the volume can change, therefore Kf and Kb changes as well and using a function to set these values may not be feasible since the function does not know the volume value.

Write a function which can change numKf <-> Kf and numKb <-> Kb and use numKf and numKb with functions.

@vinuvargheseijk
Copy link
Author

I don't have any volume change in the model. The trouble is that setNumKf works perfectly, but when it is used, the Kb of the same 'reac' don't have any role. Also, I would like to point out that this is not a problem with numKf. This is a problem with using setNumKf in the moose.connect('func','valueOut','reac','setNumKf')
Even though I used reac.Kb=some value, when the above method is used, this Kb seems to be doing nothing.
Please check the rdesigneur example in my first post to see if that is the case.

@dilawar
Copy link
Contributor

dilawar commented Apr 14, 2020

Is this behaviour specific to new version? Does is also happen with 3.1.4 or older version before exprtk was merged? I can check later by myself but if you know already that would be helpful?

@vinuvargheseijk
Copy link
Author

This issue exists in all versions. But that is OK, since I have found a way around this.

@dilawar
Copy link
Contributor

dilawar commented Apr 14, 2020 via email

@dilawar dilawar added the docs label Apr 14, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants