Hi Andrew,
Relion won’t care about the path names as long as they are correct from the current working directory and unique. If merging causes name clashes, then you'll have to link things into sub-directories (and edit the STAR file accordingly) to prevent them.
For really complex merges to keep things simple in the new project directory, I’ll often just link the aligned images into new sub-directories, modify the STAR file rlnMicrographName entries to point to them, merge the STAR files, then re-extract particles. Then you don’t need to worry about polluting your new project with references to old job directories.
> On Sep 5, 2018, at 11:58 AM, Andrew Kehr <[log in to unmask]> wrote:
>
> Hello All,
>
> I have two datasets separated by relion 2.1.0 directories from different dates which I have processed separately past the point of particle picking. I have decided I would like to combine the datasets into one of the extant directories and continue processing. When I attempt to import files and directories from outside of the current relion directory, I get errors that the files cannot be found which indicates that the software cannot look outside of the current working directory. If I were to move files and directories and edit .star files from one directory to another such that I could import them, would relion accept the fact there may now be a ManualPick/job003 (from one dataset) and a CtfFind/job003 (from the other). Or must I start entirely from scratch on one dataset by importing it into the other and moving through the pipeline again?
>
> Thank you,
> Andy
>
> ########################################################################
>
> To unsubscribe from the CCPEM list, click the following link:
> https://www.jiscmail.ac.uk/cgi-bin/webadmin?SUBED1=CCPEM&A=1
########################################################################
To unsubscribe from the CCPEM list, click the following link:
https://www.jiscmail.ac.uk/cgi-bin/webadmin?SUBED1=CCPEM&A=1
|