Can I compose a tree to have physical subtrees with different shot numbers? about mdsplus HOT 3 CLOSED

On Nov 8, 2023, at 7:13 PM, Daniel Austin ***@***.***> wrote: Affiliation Zap Energy Question I am interested in creating a collection of physical subtrees, each with their own (possibly different) shot numbers, and putting them in a parent tree with its own shot number. My motivation is that I would like to associate a physical tree with each subsystem in our device so that an experimental sequence can be run for just that subsystem by dispatching to just that physical tree while also allowing running sequences on sets of subsystems through the parent tree. One way that this would almost work is to have a parent tree that contains physical subtree nodes. I can open a subtree S, create a pulse file for it, and run the sequence. It will get a shot number, say S_1. I could then open the parent tree, create a pulse (which creates a pulse for all the subtrees be default), and dispatch across the parent pulse. The shot number for the parent pulse and all the physical subtrees it created would be 1, so P_1 and S_1. The S_1 file would collide with the subtree-only sequence file S_1 done just prior. What I would like to happen is for parent pulse P_1 to create and have a subtree reference to subsystem pulse S_2, not S_1. As far as I can tell through experimentation and some code inspection, this is not possible. A subtree reference always uses the same shot number as its parent. Is that true? Are there any ways to create a tree that has a shot number that is distinct from the shot numbers of its subtrees? If not, the alternative I can see possibly working is to manually create pulses for each physical subtree that each have their own shot numbers, then create a pulse file for the parent that has its own shot number but explicitly EXCLUDE all physical subtrees, then do some kind of _path and symlink game where I create symlinks with parent shot numbers that point to the files of subtree shot numbers. So something like P_1 contains a subtree reference to PS_1, and in the file system there is a symlink PS_1 -> S_2. I have also read in papers that some facilities create their own shot numbering association system that is distinct from MDSplus. The reason I want to do the association in MDSplus is that I want jScopes and jTraverser and everything else in the ecosystem to work when accessing a parent tree. Thanks. — Reply to this email directly, view it on GitHub <#2651>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ABY5AZPKBIIV36HH2OADWK3YDQN2RAVCNFSM6AAAAAA7DWVZ6WVHI2DSMVQWIX3LMV43ASLTON2WKOZRHE4DINJZG44DIMI>. You are receiving this because you are subscribed to this thread.