Apertures definition with FIELD_MAP  [SOLVED]

https://www.dacm-logiciels.fr/tracewin
Post Reply
Spaingonzpau
Novice
Novice
Posts: 3
Joined: Thu 24 Aug 2023 16:12
Country:
Spain (es)
Spain

Apertures definition with FIELD_MAP

Post by Spaingonzpau »

Dear colleagues,

I need to introduce a series of rectangular apertures into a sequence of superposed field maps.
To my understanding there are two ways of doing this:
1) Using FIELD_MAP with the geometry parameter of a 3D aperture map (10000).
2) Setting the aperture flag (Ka) of the first FIELD_MAP to Ka = 1.
I have some questions about both of these strategies. I attach a minimal reproducible example.

1) Using FIELD_MAP as 3D aperture map.

Even though this is a minor issue: the apertures are not plotted. Is there a way in TraceWin to obtain a file with the apertures of the whole beamline? E.g., section in x and y.

On the same line (even though this is not related to FIELD_MAP or the apertures), is there a way to obtain a file with the z (or rather s) positions of all the beamline components, except from drifts? This would be very convenient to crosscheck that the beamline skeleton agrees with the typical 2D CAD files provided by engineering teams. Maybe this "feature" is already available, but I could not find it.


2. Using aperture flag Ka = 1 of first FIELD_MAP.

a) The behaviour of TraceWin seems to depend on the calculation step. In the test example provided in the attachment, for instance, when selecting 100 steps per meter the third aperture seems to be ignored. But when selecting 100 steps per βλ, the third aperture is included but the second seems to be ignored. Am I doing something wrong?

b) As stated in the documentation, the aperture file only accepts circular or elliptical apertures. Is there any possibility to include rectangular apertures using the apreture flag Ka=1 in FIELD_MAP? This would be very convenient. Otherwise, the only alternative that I can think of is to include the aperture as a 3D aperture map with FIELD_MAP, which for a long sequence of superposed FIELD_MAP elements results in a rather large file.


System specifications:
  • OS: Windows 10
  • TraceWin version: 2.24.2.9

Many thanks in advance for your support and best regards,
Pau
Attachments
aperture tests.7z
(4.67 MiB) Downloaded 11 times
User avatar
FranceDidier
Administrator
Administrator
Posts: 1050
Joined: Wed 26 Aug 2020 14:40
Country:
France (fr)
France

Re: Apertures definition with FIELD_MAP

Post by FranceDidier »

Dear Gonzpau,

The new version of TraceWin therefore displays the beam aperture in envelope maps for 1D or 3D aperture field maps.
A new FIELD_MAP option (see FIELD_MAP manual) lets you select an elliptical or rectangular aperture for the 1D aperture field map.

Now, to save the position of the elements on the line, there are 2 solutions already available:
- In the "Data" tab, you can save all the information about the line to a file ("Save table to file" button) at the bottom left.
- In the "Charts" tab, the "Synoptic" tool allows to save the line geometries.

Finally, concerning the calculation step which, when it is too large, ignores certain values in the aperture map, yes, I can confirm that it must indeed be chosen judiciously depending on the step used in the field map describing the aperture.

Regards,

Didier
Spaingonzpau
Novice
Novice
Posts: 3
Joined: Thu 24 Aug 2023 16:12
Country:
Spain (es)
Spain

Re: Apertures definition with FIELD_MAP

Post by Spaingonzpau »

Dear Didier,

many thanks for your reply. I think you answered most of my questions. However, I still don't understand this:
A new FIELD_MAP option (see FIELD_MAP manual) lets you select an elliptical or rectangular aperture for the 1D aperture field map.
When you refer to
1D aperture field map
, do you mean when using a FIELD_MAP with the aperture flag Ka = 1? In that case, do you mean that the file "field_map_name.ouv" accepts using a rectangular aperture? If so, does the syntax follows that of an APERTURE element?

Otherwise, when using a field map with geometry flag set to aperture map (geom = 10000), I understand that the field map needs to be defined for a 3D grid for which 1 is material and 0 is space.

What am I missing? I cannot find this information in the manual, apologizes...

With regards to saving the information of the beamline in a file:
- In the "Data" tab, you can save all the information about the line to a file ("Save table to file" button) at the bottom left.
- In the "Charts" tab, the "Synoptic" tool allows to save the line geometries.
Do these options consider the possibility to save the aperture evolution of the pipe along the beamline?

Many thanks again for your support and best regards,
Pau
User avatar
FranceDidier
Administrator
Administrator
Posts: 1050
Joined: Wed 26 Aug 2020 14:40
Country:
France (fr)
France

Re: Apertures definition with FIELD_MAP  [SOLVED]

Post by FranceDidier »

Dear Gonzpau,

When flag Ka = 1 -> circular aperture read in 1D field map and when k=2, read data read are considered as rectangular apertures
Otherwise, when using a field map with geometry flag set to aperture map (geom = 10000), I understand that the field map needs to be defined for a 3D grid for which 1 is material and 0 is space.
Exactly, nothing has changed on that side.
Do these options consider the possibility to save the aperture evolution of the pipe along the beamline
The two files I've suggested will only give the position of each element, so a fieldmap will only be represented by a single position in the file, making it difficult to show a map of apertures varying along the element in question. Technically, I don't see how it can be done!

Regards,

Didier
Spaingonzpau
Novice
Novice
Posts: 3
Joined: Thu 24 Aug 2023 16:12
Country:
Spain (es)
Spain

Re: Apertures definition with FIELD_MAP

Post by Spaingonzpau »

Many thanks for the quick reply!

I have marked your last post as SOLVED, before testing the solution... When I put Ka=2 I don't see the expected behavior. I attach a minimal example. Do I need to update the TraceWin version? Or am I still doing something wrong?

Apologizes for the confusion and best regards,
Pau
Attachments
aperture tests v2.7z
(4.67 MiB) Downloaded 2 times
Post Reply