Skip to content

Comments

[discussion-187] Adding an identifier to pf_passive loop#196

Open
imbeauf wants to merge 2 commits intoiterorganization:developfrom
imbeauf:extensio/discussion-187
Open

[discussion-187] Adding an identifier to pf_passive loop#196
imbeauf wants to merge 2 commits intoiterorganization:developfrom
imbeauf:extensio/discussion-187

Conversation

@imbeauf
Copy link
Collaborator

@imbeauf imbeauf commented Jan 16, 2026

@github-actions
Copy link

@github-actions
Copy link

@imbeauf
Copy link
Collaborator Author

imbeauf commented Jan 21, 2026

Dear reviewers, only David has done his review on this PR, could you do your review ?
Thanks

Copy link
Collaborator

@SimonPinches SimonPinches left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'm not fully convinced of the need for this PR. Why do we need to associate passive loops with various objects. Shouldn't all PF passive loops be used in any calculation?
The split of passive loops between different physical objects could be done at the IDS level by having a file for cryostat, etc. Codes would then be expected to use all loops given and the choice would be made by what MD data was fed into the workflow.

<int name="vv_inner" description="Vacuum vessel inner shell" >10</int>
<int name="vv_outer" description="Vaccum vessel outer shell" >11</int>
<int name="cryostat" description="Cryostat" >12</int>
<int name="triangular_support" description="Triangular support" >13</int>
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@DavidPCoster, should the AUG passive stabilization loops appear in this list? If so, I think we need to extend this IDS to allow circuits (without power supplies) to reflect the fact that the two of them are wired in anti-series. Or are such connects PSLs always modelled as active coils / circuits without power supplies?

@imbeauf
Copy link
Collaborator Author

imbeauf commented Jan 27, 2026

I'm not fully convinced of the need for this PR. Why do we need to associate passive loops with various objects. Shouldn't all PF passive loops be used in any calculation? The split of passive loops between different physical objects could be done at the IDS level by having a file for cryostat, etc. Codes would then be expected to use all loops given and the choice would be made by what MD data was fed into the workflow.

@MaxDubrov, could you reply to this comment from Simon ?

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

Successfully merging this pull request may close these issues.

8 participants