One central dogma of Unix:
no matter how apparently absurd the error message, it's literally true.
> File: "./sc_radii.lib"
>
> Cannot be opened for reading
So, the file sc_radii.lib cannot be found in the current directory (i.e.
".") in whatever context you're running in. I rather strongly suggest
that the missing file is the literal truth here.
For the rest of the errors, the first clue is:
> sc: Use: <logical name> <file name>
Are you using the CCP4 standard method of:
sc xyzin my_file.pdb
or did you leave the xyzin part out ? xyzin is not a file name, it's
the logical unit name to which the file name becomes associated. It's a
*lot* easier to debug if you include the (part of the) script you're
actually using and not make us guess.
Cheers,
Phil Jeffrey
Princeton
On 9/29/15 2:30 PM, NISHANT SINGH wrote:
> Hi Engin,
>
> I created the file as you mentioned earlier, but I am having some
> problems with it. If I keep the "./sc_radii.lib" portion, I get the
> following error message:
>
> File: "./sc_radii.lib"
>
> Cannot be opened for reading
>
>>>>>>> CCP4 library signal ccp4_general:Cannot find input file (Error)
>
> raised in ccp4setenv <<<<<<
>
> Last system error message: No such file or directory
>
> sc: Cannot find input file
>
> sc: Cannot find input file
>
> Times: User: 0.0s System: 0.0s Elapsed: 0:00
>
>
> I also tried removing the sc_radii.lib section, and I got the following
> error message:
>
>
>>>>>>> CCP4 library signal ccp4_general:Use: <logical name> <file name> (Error)
>
> raised in ccp4fyp <<<<<<
>
> sc: Use: <logical name> <file name>
>
> sc: Use: <logical name> <file name>
>
> Times: User: 0.0s System: 0.0s Elapsed: 0:00
>
> ./sc.sh: line 5: MOLECULE: command not found
>
> ./sc.sh: line 6: CHAIN: command not found
>
> ./sc.sh: line 7: CHAIN: command not found
>
> ./sc.sh: line 10: END: command not found
>
> ./sc.sh: line 11: eof: command not found
>
|