Body

Hello Marton and Roberto.

It's seem to me that there are some bugs in the procedure for field values calculations in the Synrad regions. I mean the mode 2 option (Coords along a direction). If I put there a Mag file with more complicated profile than it’s exampled in Synrad documentation, the trajectory became stochastic and I see a huge field values in the intermediated points. I can send a MAG file as well as region param file by e-mail. Can you explain me where I failed?

Regards.

Konstantin Zolotarev, BINP/

zolotarev@inp.nsk.su

Submitted by Marton Ady 6 years ago

Dear Konstantin,

 

Indeed it would be nice to know whether it's a bug or an incorrect file format. You can upload the file here (see https://molflow.web.cern.ch/content/changes-inserting-files-and-images-comments) or send me by email (marton.ady@cern.ch) and I'll hve a look.

 

Submitted by b07ce711d30528bb3dc0 6 years ago

p.mag p1.mag wg_n.param

Dear Marton.

Here are my files. At first,I tried to use complicated realistic profile which present in the p.mag file. It's a real profile (measured) for our multipole wiggler.

Later I tried to use simpler profile, which present in the p1.mag file. But also I did not reach suscsess.

In both cases, I use same param file (wg_n.param).

Thank you for your help.

Regards.

Konstantin.

 

Submitted by Marton Ady 6 years ago

Thank you!

The problem with the file is the last number of the first line: it's 1 in both files, whereas it should be N denoting the number of coordinates to read (the full format is 

period dirX dirY dirZ N

)

I've changed it to 21 in p1.mag and got the following region, which seems correct:

2017-06-19 14_33_53-Synrad+ 1.4.8 (Apr 3 2017) [].png

I know that the beginning is difficult with Synrad, good luck with the unusual file formats, and get back to me when stuck!

Marton

Submitted by b07ce711d30528bb3dc0 6 years ago

 

 

 

Hello Marton.

Thank you very much.

I didn't corectly catch N meaing.

Konstantin