Ticket #1171 (closed: fixed)

Opened 11 years ago

Last modified 5 years ago

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

comment:1 Changed 10 years ago by Anders Markvardsen

(In [4281]) Allow nested translation using a notation like

<location r="10" t="90">

<trans r="8" t="-90" >

<trans z="2" >

<trans z="1" />

</trans>

</trans>

</location>

Sorted out a bug in LoadInstrument where parameters were not populated correctly. Thanks to Roman for helping with fixing this bug. Refs #1171.

comment:2 Changed 10 years ago by Anders Markvardsen

(In [4289]) Included further tests and updated wiki. Refs #1171.

comment:3 Changed 10 years ago by Anders Markvardsen

  • Status changed from new to accepted

comment:4 Changed 10 years ago by Anders Markvardsen

  • Status changed from accepted to testing
  • Resolution set to fixed

comment:5 Changed 10 years ago by Steve Williams

  • Status changed from testing to closed

comment:6 Changed 5 years ago by Stuart Campbell

This ticket has been transferred to github issue 2019

Note: See TracTickets for help on using tickets.