You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi,
is there a possibility in detl too see which units/reactors were used? Sometimes only 6 of our 8 reactors are used but not in a chronological order. For example we used reactors 1,2,5,6,7,8 which shows in detl like this:
It can be seen that 8 would be the maximum. When I want to adress them directly. For example ddata[1].dataframe.head() is for unit 1. ddata[3].dataframe.head() is for the third consecutive unit which is in our case unit 5, because 3&4 are empty. Is there a way to adress the units directly by unit number or unit name (something like 'unit 5')? That would be very helpful for us.
Thank you for your feedback!
The text was updated successfully, but these errors were encountered:
Hi @fisseb4, sorry for not responding for so long.
I just checked the implementation: In our test datasets it looks like Identifier can be user customized, that's why I didn't use it as the primary key.
The number I used for the primary key is the Setup #. I don't know how that correlates with the unit number though, because I don't run fermentations myself and our tests datasets all use all available units.
If there's a field that would be more suited as the primary key I'm open to making that change.
Hi,
is there a possibility in detl too see which units/reactors were used? Sometimes only 6 of our 8 reactors are used but not in a chronological order. For example we used reactors 1,2,5,6,7,8 which shows in detl like this:
It can be seen that 8 would be the maximum. When I want to adress them directly. For example
ddata[1].dataframe.head()
is for unit 1.ddata[3].dataframe.head()
is for the third consecutive unit which is in our case unit 5, because 3&4 are empty. Is there a way to adress the units directly by unit number or unit name (something like 'unit 5')? That would be very helpful for us.Thank you for your feedback!
The text was updated successfully, but these errors were encountered: