Ticket #1171 (closed: fixed)
Allow nested translation in instrument definition file
Reported by: | Anders Markvardsen | Owned by: | Anders Markvardsen |
---|---|---|---|
Priority: | major | Milestone: | Iteration 23 |
Component: | Keywords: | ||
Cc: | nick.draper@… | Blocked By: | |
Blocking: | Tester: |
Description
Currently allowing for nesting rotations within a <location> element to define the location of a component in an IDF.
Extend this to also allow nested translation using the notation
<location r="1" t="0" p="0">
<trans r="1" t="45" p="0" />
</location>
This has the effect of first translating the component along the z-azis by 1 and then from this position translating according to r="1" t="45" p="0" which correspond to x=sqrt(2) y=0 and z=sqrt(2) in cartesian coordinates.
This feature would for example be useful in the description of the ENGINE-X instrument.
Change History
Note: See
TracTickets for help on using
tickets.
(In [4281]) Allow nested translation using a notation like
Sorted out a bug in LoadInstrument where parameters were not populated correctly. Thanks to Roman for helping with fixing this bug. Refs #1171.