Hi,
I'm trying to make cisTEM run on a shared university cluster, and struggling through making it play nicely with TOQUE, PBS, etc. According to the documentation, I can create a file called default_run_profiles, put it in the bin directory with the cisTEM binary and voila, everyone who runs cisTEM will have access to the profiles described in that file. This seems to work on _new_ projects, but not on projects that have already been created. This isn't completely terrible, but certainly not ideal. Is there some way to _force_ older projects to read and use this file?
Related to running on the cluster, where does cisTEM keep track of the list of recent projects shown when starting the GUI and is there a "best practice" for totally removing a project?
Thanks for any help that can be offered.
Hi,
You can't force old projects to add them, but you can import the same text file into open projects through settings->run profiles->Import.
The recent projects are kept in a file called .cisTEM in the users home directory.
I'm not sure about what you mean by totally removing a project. You should be able to just delete it from disk? If you don't want it to appear in recent projects, you can edit the .cisTEM file, but you can also just ignore it.
Cheers!
Tim
Tim,
Thanks. I do realize that people can import the profiles into an existing project, but since I have no idea who on the cluster might have already opened projects, I have no way of tell them to do that. At least I can make sure that the new projects have my new profiles (and can use the queue instead of only running on the login nodes...).
With regard to "removing a project," one of the users I am teaching to run cisTEM totally screwed up her first attempt at the tutorial and wanted simply to delete it all. She and I both know that she can just delete the directory, but that (as you noted) still leaves it as a recent project. Most of my new users are confused enough trying to use linux and all these strange programs, so anything I can do to simplify life is useful. Manipulating the .cisTEM file is exactly what I was looking for, and for whatever reason, I didn't notice that file when I was looking for something like it.
Again, thanks for your help.