hanskanns

Quote

 a bit of complexity to the formula

thats good 🙂

Step by step I´m understanding how to work with capsules and formulas. Magnificent whats possible there.

Thanks again.

Thanks for asking about that John B.
It is a batch process (reactors) which then starts to be a continuous process.
The general idea is to track how long each reactor batch (based on volume calculations)
is how long (residence time) in the following UnitOperations.
What we basically calculated so far (examples above) are the timeframes when something comes
from the reactors (dynamic reset signal pink capsules, goes to the first UO -> blue capsules).
And the blue capsules are longer then the pink ones, because it is diluted and the product resides longer in that UO as the next Reactor-batch arrives...

So I was thinking it might be interessting to put that blue capsules one after another,
to basically ignore the dilution effect and just keep on the volumes, but after rethinking
that would be not a right calulation, because as you mentioned if would delay the blue capsules
more and more to the past and ignore the dilution, which is not realistic.

I hope that desciption is understandable?

I´m at the same time impressed by the capabilities of Seeq and thankful for your help.

Works perfectly also for my use case, only had to add one little thing (since I do not have the Unit inside the capsule property)

$end_value = $start_value + ($c.property('Rvol')).setUnits('L')

Feeling already sorry for all my questions, but maybe one more follow up questions more:

Is it also possible that on that resulting overlapping capsules, starting with capsule 1, the durations will stay, but the start key of capsule 2 will be put directly after the end of capsule 1 and so on with all the capsules?

I´m thinking about something like:

$condition2.transform($c -> // to loop over each capsule
	$c.setProperty('min_for_vol', // create a new property
		floor($flow_integral_signal/$c.property("Rvol")) // for the first time the liters from the this capsule-property passed on the flow signal
			.toCondition()
			.removeLongerThan(3d)
			.ToGroup($c)
			.pick(1).duration().convertUnits('min')
))

It still does not behave as I need it, but it might be in the right direction for my usecase. The generated capsules / times are way to short now.

For the floor calculation, does the capsule start also need to be defined if it should start it at the beginning of each capsule?

Next step could be to generate a signal / condition based on the new capsule property.

Thanks, it runs perfectly within this example, unfortunalty my real data is different 😉

It is a continuous process which I like to chunk into UnitOperations based on Volume Calculations.

Tried to sketch my usecase:

The Problem is that on my data the capsules which have the reset information are actually to
small that the runningSum (integral) in it can reach the reset_quantity

What I´m trying to achieve:
everytime a capsule starts of the initial condition1 -> start doing the integral running sum L/min of the flow,
until a dynamic limit is reached (based on the capsule properties, per capsule on condition1, one after another)

and finally get a signal / condition(capsules)

thanks alot in advance, really appreciate all that very beneficial input from this Seeq forums

A follow up question on this: Could the formula / logic be extended to have the $reset_quantity not be static but been read from another capsule property?

F.e. Sum up over the year, but there are capsules each $month which have different liters per month to be used as $reset_quantity?

Thanks

thank you, that is what I was looking for

thanks alot works 👍

I have a flow in and flow out in l/h at a tank. What I´m trying to achieve is count up the flow in and flow out and get a capsule once a specific amount of liter as passed the tank, then reset and count up for next capsule.

Convert signals toStep() ? and then make a runningSum(), save as variable and stop when the volume reached.

Can that be depicted in one formula?

Thanks for the hint Joe, I checked the composite Condition but I still don´t figured out yet how to:

after rethinking I need to re-specify what I´m trying to achieve. On the same capsule layer, on the first found Capsule-1 extend the end of this Capsule-1

until the start of Capsule-2. Then again extend Capsule-3-end until start of Capsule 4 and so on.

To only make this on the capsule-pairs 1/2 3/4 5/6 ... maybe somehow count up?

Thanks a lot Joe for you fast feedback. The property is already there, but without "re"-setting them, looks like they don´t get transferred.

The second formula works like a charm. 👍

edit: was a mistake on my side when using 

combinewith($r1tr, $r2tr, $r3tr)

it also takes the capsule properties

I would like generate new capsules, grouped as -> start of capsules from first capsules until end of second capsules

When doing just a union $c = $a.union($b) the capsules in $c are not getting grouped as needed.

thanks for any help

Hello together, I´have been struggling with the following:

There are 3 conditions, each of them having the property @ the capsules 'Reactor'.

I want to bring them into one (bottom line) and based if it´s from 1,2 or 3 set the property at the result 'Reactor' to 1,2 or 3

Any ideas?

I´m planning to do the following but I´m not sure if this is feasable via the seeq Rest api and Python

There is a Seeq "Template" (a monthly Report) -> a Organizer Topic with 1 Page (document).
Within this document are some data-ranges defined and there are some text fields (with f.e. the Name of the regarding month)

If a new month begins, python will have the name of the just finished month together with the data ranges.

Now can this be automated via the seeq-rest-api: ?
Use the "Template" document and create a new document in another Organizer Topic, rename it, modify the data-ranges,
automatically update the linked seeq content of the page and rename some text fields (with f.e. the Name of the regarding month)
As far I know, there is only the Date Ranges Variables in the Org. Topic, so I guess it is difficult to update the text fields.

Thanks alot guys for you help. Working now

from seeq import spy
from seeq import sdk
spy.login(access_key="CagR-n4oQGqjlAb7e6fr3B", password="Ec9DaXnSXgaG969cjkv4d4iGdGiAah" ,url="https://myseeqserver")
items_api = sdk.ItemsApi(spy.client)

# f.e.
items_api.get_item_and_all_properties(id='4F88E997-FAAA-431E-873F-DEE98F0E653B')

3 minutes ago, Sanman said:

Check this post out: How to use the Seeq API/SDK in Python/Seeq Data Lab - Seeq Data Lab - Seeq Community Website

Thanks I already checked that Page. It is still no clear for me, which lines to code to do the auth with an access_key

Hello together, I can connect to a seek server api (via access_key) without problems
with the seeq.spy module from
https://pypi.org/project/seeq/

Does anyone know how connect with the seeq.sdk module from this package using a seeq access_key ?