unable to write String_File ???

Robert Knop wrote on Feb 01, 1999

I'm at a bit of a loose end.  I'm trying to run ccdproc from within the
package MSCRED.  Now, when I do it, it dies, giving the error message:

ERROR on line 208: No write permission on file (String_File)
    ccdproc (images=obj048)

I fear I don't understand this.  I've tried looking at ccdproc.cl in the
mscred directory hierarchy, but cannot find any reference to String_File.
Line 208 is right near the end of the script.  The directory where I'm
running I have write permission to, and I have write permission to the
file I'm trying to run it on.

ccdproc worked for me the other day; I'm not sure what might have changed.
Can anybody suggest to me where I might look to try and figure out what's
hanging things up here?

Thanks,

-Rob

=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
==== Rob Knop ===== rknop@lbl.gov ====== http://panisse.lbl.gov/~rknop ======

---

Frank Valdes wrote on Feb 02, 1999

Hi Rob,

The "String_File" error is generally caused by some other error occuring
in a task which is not properly trapped by the task and then eventually
causing memory corruption errors.  The specific error has to do with 
in memory writing using a psuedofile and so it does not have anything to
do with real file permissions.  The error is coming from one of the
compiled tasks called by ccdproc.cl and not from the script.  The line
number reported when an error occurs in a script is generally not very
useful.  So the answer is I don't know what is causing the error or what
it means.  The only way to help is to reproduce the problem on your machine
or here.  The first thing for you to try is to unlearn things and try
again.  It may be that some parameter got set wrong.  If the problem
is very reproducible then I can suggest some debugging output to collect
which might shed some light on the matter.  Let me know how things stand
and if you need help getting this resolved and I'll give you list of some
things to send.

Cheers,
Frank Valdes

---

Robert Knop wrote on Feb 02, 1999

> The "String_File" error is generally caused by some other error occuring
> in a task which is not properly trapped by the task and then eventually
> causing memory corruption errors.

Erg.  I figured out the problem; it's the classic "filename length too
long" problem.  I had a 58-character filename (an absolute path) for the
domeflat.  When I put the flat in the current directory (really, a symbolic
link), the problem went away.  The error was bizarre, and didn't suggest
a too long filename... but I should have realized that that was one of the
things to check first.

-Rob

=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
==== Rob Knop ===== rknop@lbl.gov ====== http://panisse.lbl.gov/~rknop ======

---

Last post on Feb 02, 1999