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.

Sign up for GitHub

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

Jump to bottom

for fields, should blueprint_index require the field type? #42

Closed
cyrush opened this issue Sep 14, 2016 · 1 comment
Closed

for fields, should blueprint_index require the field type? #42

cyrush opened this issue Sep 14, 2016 · 1 comment
Labels
design
Projects
Blueprint

Comments

@cyrush
Copy link
Member

cyrush commented Sep 14, 2016

"scalar", "vector", etc

could be redundant with number_of_components, but may be needed in some cases to differentiate between a generic nd-array and say a vector or a tensor.
@cyrush cyrush added the task label Sep 14, 2016
@cyrush cyrush changed the title for fields, should blueprint_index contain the field type? for fields, should blueprint_index require the field type? Sep 14, 2016
@cyrush cyrush added design and removed task labels Sep 17, 2016
@cyrush
Copy link
Member Author

cyrush commented Oct 11, 2018

I am going to close this for now, I haven't seen the need. I expected to see it in the context of VisIt, but there hasn't been a strong need.

@cyrush cyrush closed this as completed Oct 11, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
design
Projects
Blueprint
Discussions
Milestone
No milestone
Development

No branches or pull requests
1 participant
@cyrush