pressure jump outline

[stan-dot]

not sure about the wiring

[codecov]

Codecov Report

Attention: Patch coverage is 0% with 92 lines in your changes missing coverage. Please review.

Project coverage is 33.86%. Comparing base (1f0a008) to head (a471396).

Files	Patch %	Lines
src/i22_bluesky/plans/pressure_jump.py	0.00%	92 Missing ⚠️

❗ There is a different number of reports uploaded between BASE (1f0a008) and HEAD (a471396). Click for more details.

HEAD has 3 uploads less than BASE

Flag	BASE (1f0a008)	HEAD (a471396)
	6	3

Additional details and impacted files

@@             Coverage Diff             @@
##             main      #97       +/-   ##
===========================================
- Coverage   47.96%   33.86%   -14.10%     
===========================================
  Files           9       10        +1     
  Lines         221      313       +92     
===========================================
  Hits          106      106               
- Misses        115      207       +92     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

[DiamondJoseph]

row for the triggering , hold the pressure cell trigger high until end of experiment

[stan-dot]

? not sure what does that mean - should I add this as documentation, or add another row to hold?

[stan-dot]

@DiamondJoseph any updates?

[stan-dot]

actually all the outs are set to True in all the other frames

[stan-dot]

todo: update with notes from the meeting

[stan-dot]

1, 3 pressure must be less than 50 bar. for rise 5 mst be open, for loss 6 must be open

transducer aka chamber
p1 pump, p2 intermediate, p3 sample
static scanspec

read for cell - 3

pump is fast

configuration is jsut 11 PVs; 3 per valbe, and fast ones as extra

on joining the volumes, the pressure would fall

we do not want any air, it would cause the diagram to wobble and various issues

the physical orde ris pump - v3 - inter -> v5/v6 - celll

match inter pressure cell pressure, then just raise the pump

there are some plugins

in GDA there is pressure_from, pressure_to, etc, and old style of TFG table "1110111" etc binary string

[stan-dot]

todos

• start the plan with the confirmation of values

1, 3 pressure must be less than 50 bar. for rise 5 mst be open, for loss 6 must be open

• make a stub just to adjust those, add it to a third plan
• just increase the pressure and assert that it's higher at the end
• ignore the detectors for the small test

[stan-dot]

ideally should take into account this issue too DiamondLightSource/dodal#759