This is not an error, it was done in such a way just for simplicity: when the
task starts it makes the file.error with such words, and it is to be changed
only when (if) the task completes successfully.
Best wishes,
Lyudmila Dobysheva
--
13 may 2024г., 22:24 +04:00 from Straus, Daniel B [email protected]:
>The jobs seem to be running okay, but there are nondescript messages in the
>.error files I am trying to figure out.
>For instance, when running a 4 node job with parallel LAPW0, as soon as the
>job starts, lapw0.error shows “Error in LAPW0”, but the job keeps running, and
>when LAPW0 completes, lapw0.error is blank. Similarly, as soon as LAPW1
>starts, uplapw1_1.error
shows “Error in LAPW1” (but uplapw1_2, _3, and _4 are blank), and uplapw1.error
shows “** Error in Parallel LAPW1”. However, the job steps keep running, and I
cannot find any more descriptive error messages. Stdout shows no printed error
messages—for LAPW0,
the only message printed to stdout is LAPW0 END.
>Daniel Straus
>
>Assistant Professor
>
>Department of Chemistry
>
>Tulane University
>
>5088 Percival Stern Hall
>
>6400 Freret Street
>
>New Orleans, LA 70118
>
>(504) 862-3585
>
>http://straus.tulane.edu/
>
>
>
>
>
>
>
>
>_______________________________________________
>Wien mailing list
>[email protected]
>http://zeus.theochem.tuwien.ac.at/mailman/listinfo/wien
>SEARCH the MAILING-LIST at:
>http://www.mail-archive.com/[email protected]/index.html
>
>
>
_______________________________________________
Wien mailing list
[email protected]
http://zeus.theochem.tuwien.ac.at/mailman/listinfo/wien
SEARCH the MAILING-LIST at:
http://www.mail-archive.com/[email protected]/index.html
