Correctly implementing a conical aperture

https://www.dacm-logiciels.fr/tracewin
Post Reply
United States of Americajyosk001
Neophyte
Neophyte
Posts: 19
Joined: Thu 19 Feb 2026 21:00
Country:
United States of America (us)
United States of America

Correctly implementing a conical aperture

Post by United States of Americajyosk001 »

Hi Didier,

I'm having trouble figuring out how to correctly implement a conical aperture in TraceWin.

As an example, I made an aperture map called conicalaperture.ouv, representing a conical aperture with initial & final radii of 25 mm and 12 mm respectively over a longitudinal length of 400 mm. When I try to implement this, I get an error saying "Inconsistent range (Max,min) defined in the geometry field map file."

I've attached example project files. What am I doing wrong?

Thanks,

Josh
Attachments
ApertureMapTest.dat
Data File
(97 Bytes) Downloaded 14 times
ApertureMapTest.ini
Project File
(43.77 KiB) Downloaded 11 times
conicalaperture.ouv
Aperture Map
(14.49 KiB) Downloaded 9 times
User avatar
FranceDidier
Administrator
Administrator
Posts: 1367
Joined: Wed 26 Aug 2020 14:40
Country:
France (fr)
France

Re: Correctly implementing a conical aperture

Post by FranceDidier »

Dear Josh,

You are confusing two ways to define an opening in FIELD_MAP.
The first method, corresponding to the "Ka" flag in FIELD_MAP, involves adding a file with the .ouv extension to the descriptions of the magnetic or electric fields in FIELD_MAP.
https://dacm-codes.fr/Softwares/TraceWi ... erture_map
This is apparently what you wanted to do, but it must necessarily be associated with a magnetic or electric field map files.

The second method involves defining a 3D map that precisely describes the element’s geometry (3D format described here:https://dacm-codes.fr/Softwares/TraceWi ... r_electric ). This map must indeed have the “geom” parameter in FIELD_MAP set to “10000.”

So in your case, I suggest creating a 1D magnetic field map file named “conicalaperture.bsz” with zero field value set to 0, so that you can use the “Ka” flag
The syntax would be “FIELD_MAP 010 400 0 100 0 0 0 1 conicalaperture”

I realize that all of this isn't necessarily very clear, but as we keep adding multiple and varied requests, the tool becomes much more complex.

Regards,

Didier
United States of Americajyosk001
Neophyte
Neophyte
Posts: 19
Joined: Thu 19 Feb 2026 21:00
Country:
United States of America (us)
United States of America

Re: Correctly implementing a conical aperture

Post by United States of Americajyosk001 »

Hi Didier,

Thanks! I got it to work. Just as future reference for other users who might be interested, I was able to accomplish this by creating two files of the same name but with different extensions: conicalaperture.ouv containing the aperture geometry (z, Xmax, Ymax) and conicalaperture.bsz containing a short 1D magnetic field map with zero field strength. I then used the line:

FIELD_MAP 010 400 0 100 0 0 0 1 conicalaperture

Though the two files have different amounts of data and apparently different zmax's, it still was able to create the conical aperture with the correct initial/final radii and length. Not sure if this was the correct and/or simplest way to do this, but it seems to work.

Thanks,

Josh
Attachments
ApertureMapTest.dat
(95 Bytes) Downloaded 8 times
conicalaperture.ouv
(14.49 KiB) Downloaded 7 times
conicalaperture.bsz
(103 Bytes) Downloaded 8 times
User avatar
FranceDidier
Administrator
Administrator
Posts: 1367
Joined: Wed 26 Aug 2020 14:40
Country:
France (fr)
France

Re: Correctly implementing a conical aperture

Post by FranceDidier »

Dear Josh,

Actually, that's not a problem, but why didn't you just put the correct length in your bsz file?

Regards,

Didier
Francegwhitlock71
Beginner
Beginner
Posts: 8
Joined: Sun 1 Nov 2026 03:48
Country:
France (fr)
France

Re: Correctly implementing a conical aperture

Post by Francegwhitlock71 »

Didier wrote:Actually, that's not a problem, but why didn't you just put the correct length in your bsz file?
Didier, what length did you actually put in the bsz file then, out of curiosity?
Post Reply