-
Notifications
You must be signed in to change notification settings - Fork 56
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
Stock solutions / multicomponent samples / mixtures for reactions or reaction series in variations tool #2301
Comments
Dear @HueppeH, we have a test instance where you could try the new mixture (multicomponent samples) functionality. I will discuss the points you mentioned with my team. In the meantime, maybe you can take a look at it here. When the mixture usage in the reaction scheme is finished, which we are currently working on, the points you raised here are largely addressed. You are more than welcome to let us know your feedback on our current mixture implementation. |
Dear @TasnimMehzabin , thanks for your answer. I signed up for the test instance but I was unable to find the new mixture functionality you mentioned. Could you give me a hint were to find this functionality? |
Thank you very much for the Videos, they help a lot. I simply did not see the Sample Type options. I will test, if this feature covers my use cases. |
I tried the feature but, I am insecure about the intention and functionality of some fields. Especially the lock function is not clear to me. As mixture is a rather complex feature, do you have any documentation on this which could explain some of the functions and dependencies? |
I will soon update the documentation and update you. Thank you. |
Dear @TasnimMehzabin , Thanks for the link to the documentation. I have one major question: what does "stock" in the context of the mixture sample mean? Because I would use the mixture sample to create stock solutions to use in my reactions and not necessarily a stock to create these mixtures. |
Description
Please provide a description of:
The text was updated successfully, but these errors were encountered: