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

Add sets to Database for the MaterialProcess subclasses #1922

Closed
Tracked by #1905
anastasiyaprymolenna opened this issue Apr 12, 2024 · 5 comments
Closed
Tracked by #1905

Add sets to Database for the MaterialProcess subclasses #1922

anastasiyaprymolenna opened this issue Apr 12, 2024 · 5 comments
Assignees

Comments

@anastasiyaprymolenna
Copy link
Contributor

Currently, no sets exist to be able to store the information that the MaterialProcess subclasses hope to capture. There will need to be sets written in for each subclass so the ids of the entries can be used by ProtocolExecution (which also needs a set) class to organize the individual sets into a sequence of processes.

@turbomam
Copy link
Collaborator

@turbomam
Copy link
Collaborator

We should use an aggregative material_processing_set slot, not one slot for each subclass

@turbomam
Copy link
Collaborator

@anastasiyaprymolenna
Copy link
Contributor Author

but that set is specifically for a PlannedProcess. Can we include each instance of the MaterialProcessing subtypes in that set?

@anastasiyaprymolenna
Copy link
Contributor Author

I will close this issue based on Mark's comments, because we can put all the information we need about the MaterialProcessing subclasses on the planned_process_set

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants