Change the optimizer's path of a new directory

Moderators: michael_borland, soliday

Post Reply
Xavier Nuel
Posts: 12
Joined: 15 Apr 2013, 07:49
Location: Synchrotron Soleil (France)

Change the optimizer's path of a new directory

Post by Xavier Nuel » 21 Aug 2013, 11:13

Hi there!

I ran the optimizer in the directory /home of my cluster with good results. Now I want to run it in another directory (/lnec) because /home has a limited memory. I copied exactly the same /home's files in the new directory and I tried to run the optimization in this new directory. But I have this error message in the .log files

Error:
Unable to access file optim1-000039-linear.fin--file is locked (SDDS_InitializeOutput)
running elegant for chromaticity, DA, LMA
Check /lnec/sources/physmach/gavaldax/mogaRing2/optim1-000039-main.log for status
tracking: Error:
file optim1-000039-linear.param does not exist in search path (InitializeInputFromSearchPath)
optim1-000039.inp optim1-000039-linear.fin
** Problem copying ./optim1-000039.twi to /lnec/sources/physmach/gavaldax/mogaRing2/optim1-000039.twi: error copying "./optim1-000039.twi": no such file or directory
** Problem copying ./optim1-000039.proc to /lnec/sources/physmach/gavaldax/mogaRing2/optim1-000039.proc: error copying "./optim1-000039.proc": no such file or directory
** Problem copying ./optim1-000039.param to /lnec/sources/physmach/gavaldax/mogaRing2/optim1-000039.param: error copying "./optim1-000039.param": no such file or directory
** Problem copying ./optim1-000039.aper to /lnec/sources/physmach/gavaldax/mogaRing2/optim1-000039.aper: error copying "./optim1-000039.aper": no such file or directory
** Problem copying ./optim1-000039.mmap to /lnec/sources/physmach/gavaldax/mogaRing2/optim1-000039.mmap: error copying "./optim1-000039.mmap": no such file or directory
** Problem copying ./optim1-000039.w1 to /lnec/sources/physmach/gavaldax/mogaRing2/optim1-000039.w1: error copying "./optim1-000039.w1": no such file or directory
** Problem copying ./optim1-000039.naff to /lnec/sources/physmach/gavaldax/mogaRing2/optim1-000039.naff: error copying "./optim1-000039.naff": no such file or directory
** Problem copying ./optim1-000039.fin to /lnec/sources/physmach/gavaldax/mogaRing2/optim1-000039.fin: error copying "./optim1-000039.fin": no such file or directory

The matchTemplate.ele script is not run.

I suspect that in somewhere of the original process in /home, the path of the files are defined in the original directory /home. Then, when I try to run the optimizer in the new directory, the new process can not replace the old path with the new one and the process is stopped.
In my case, How can I change the /home's path to run the optimizer in /lnec? In general, How can I change the path of the original files to run the optimizer in another directory different from the original used?

Thanks,

Xavier

michael_borland
Posts: 1927
Joined: 19 May 2008, 09:33
Location: Argonne National Laboratory
Contact:

Re: Change the optimizer's path of a new directory

Post by michael_borland » 16 Sep 2013, 08:30

Xavier,

The optimizer should do everything in the subdirectory in which it started. I'm not sure why it would behave differently in your case.

--Michael

Faissal
Posts: 16
Joined: 11 Jan 2017, 14:53
Location: Diamond Light Source (UK)

Re: Change the optimizer's path of a new directory

Post by Faissal » 22 Aug 2017, 11:01

Good evening,

I have exactly the same issue, with the same function and the same error message: I copied a folder into another one to run the tracking function, and in this new directory, the code does not seem recognize the existence of the sdds_beam input file:


the error message is the following (using Elegant 32):

Error:
file input_coords_68mm.sdds does not exist in search path (InitializeInputFromSearchPath)
Problem opening beam input file input_coords_68mm.sdds

felix_armborst
Posts: 10
Joined: 23 Aug 2017, 09:06

Re: Change the optimizer's path of a new directory

Post by felix_armborst » 23 Aug 2017, 09:15

Hi,

Had the same problem and found out it was due to me actually putting a semicolon after the filename as shown in the manual.

Best, Felix

Faissal
Posts: 16
Joined: 11 Jan 2017, 14:53
Location: Diamond Light Source (UK)

Re: Change the optimizer's path of a new directory

Post by Faissal » 29 Aug 2017, 07:56

Hi,

I found the origin of the error: in this case, it was coming from the processJob script: there is a stage where it copies the required processor files into a temporary directory, and the input beam sdds file was not listed. As a result, even though it was indeed present in the directory, it was not copied into the temporary one, and was therefore "not found".

Faissal

Post Reply