-
Notifications
You must be signed in to change notification settings - Fork 26
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
Local Scope #787
Comments
@bmaclach I think Drasil now has some features close to this. Can this be implemented now? |
@JacquesCarette It does look like data definitions now have a scope field. I don't think it currently does anything, but there's at least something there to build off of. |
We discussed this issue in our "cold cases" meeting on Dec 6, 2021. We decided that it is premature to address it now, since we are in the midst of rethinking how we think about Drasil knowledge in terms of theories. Once the new theories "model" is in place we can return to this issue. |
If we consider chunks to be theory presentations (theories definitions in CAS 760 or the unified theories we've been discussing recently), then I think almost any theory would be able to define new symbols as constants. I haven't thought about this enough, but I want to get the idea down and shared in case anyone else has thoughts. I'll definitely return to this. |
In the future, Drasil should support the idea of a local scope for symbols. As pointed out in the case studies repo:
smiths/swhs#35 (comment)
there are cases where a local scope would be helpful. The definition of \tau_w could be local to the instance model that defines the governing ODE. However, as currently set-up, we need a separate data definition to include the equations that define the local parameters \tau_w ( and \eta).
The text was updated successfully, but these errors were encountered: