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

Extract Type Information from Symbol #1558

Open
samm82 opened this issue Jun 14, 2019 · 2 comments
Open

Extract Type Information from Symbol #1558

samm82 opened this issue Jun 14, 2019 · 2 comments
Assignees
Labels
artifacts design-variability 'choices': For software families, we need design variabilities, not just requirements variabilities. needs-clarification Needs a clear 'state', 'goal', 'analysis', and 'explanation' to reduce solution ambiguities.

Comments

@samm82
Copy link
Collaborator

samm82 commented Jun 14, 2019

This was brought up in our Drasil meeting yesterday when discussing Projectile. We should be able to "extract" some typing information from the symbol, in particular, vector information. Vectors (ie. quantities with bolded symbols, although potential overlap with tensors was brought up) would be printed with "vector" after the quantity when using phrase. For example, if accel is defined with the term "acceleration" and the symbol vec lA, phrase accel would output "acceleration vector". @smiths and @Mornix should be able to fill in any gaps in this issue.

Related - "scalar" should also be extracted (if not, removed)

@samm82 samm82 added the design Related to the current design of Drasil (not artifacts). label Jun 14, 2019
@smiths
Copy link
Collaborator

smiths commented Jun 14, 2019

Further to what @samm82 said, I believe we all thought it was a good idea to automatically generate the word vector to go along with the phrase. The conversation was started with my request to @samm82 to add the word vector to distinguish the scalar acceleration (symbol a) from the vector acceleration (symbol \bf{a}). The motivation for this question is to see if you anticipate any unwanted surprises from making this change.

@JacquesCarette
Copy link
Owner

I completely agree with having our chunks carry some type information that can be queried. If this isn't already possible (I think it is), it ought to be.

Whether we want phrase to always use the type information to insert some words, that's less clear to me. That we want a combinator that does that? Most definitely. But my feeling is that modifying phrase itself is not going to do what you really want.

@balacij balacij added design-variability 'choices': For software families, we need design variabilities, not just requirements variabilities. artifacts needs-clarification Needs a clear 'state', 'goal', 'analysis', and 'explanation' to reduce solution ambiguities. and removed question design Related to the current design of Drasil (not artifacts). labels Apr 26, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
artifacts design-variability 'choices': For software families, we need design variabilities, not just requirements variabilities. needs-clarification Needs a clear 'state', 'goal', 'analysis', and 'explanation' to reduce solution ambiguities.
Projects
None yet
Development

No branches or pull requests

4 participants