On 3/6/12 1:31 PM, Irene Newhouse wrote: > I've installed Modeller9.10 on my Centos 62. linux station. I had an > earlier version working under Centos 5.x. Now I find that if I set an > alias I call mod9v10 to point to modeller9.10_x86_64-intel8 in > analogy to the alias I successfully set to its analog previously
There's no need to do that - there's already a script called mod9.10 which does basically that, which ships as part of Modeller. But we generally recommend to use Python instead if you can.
> Furthermore, I get an error indicating that my > .ali file can't be found& I've triple-checked to make sure I've > entered the name correctly.
Are you sure it's complaining about the .ali file and not something else? Or maybe you're running in the wrong directory.
> There is no modpy.sh in the directory to which the web pages point.
If you installed the RPM, there is no modpy.sh because it isn't necessary. You can just run your regular system Python, e.g. "python foo.py".
> it cannot find the equivalent of foo.py unless I give the full path to foo.py
If you're trying to run "foo.py" in the current directory by just typing "foo.py", that typically won't work on a Unix system since the current directory isn't usually in your path. Try "./foo.py" instead.
> When I specify the full path, I get error > messages such as "from: command not found"& a crash, indicative of > a massive failure to access python.
This sounds like you have tried to run the Python script as a shell script. Either prefix it with "python", as above, or add "#!/usr/bin/python" to the first line of your Python script to tell the system to use Python to run it.
Ben Webb, Modeller Caretaker