5. Errors

OINK tries to flag errors and print informative error messages so you can fix the problem.

If you get an error message about an invalid command in your input script, you can determine what command is causing the problem by looking in the log.oink file or using the echo command to see it on the screen. For a given command, OINK expects certain arguments in a specified order. If you mess this up, OINK will often flag the error.

Generally, OINK will print a message to the screen and logfile and exit gracefully when it encounters a fatal error. Sometimes it will print a WARNING to the screen and logfile and continue on; you can decide if the WARNING is important or not. If OINK crashes or hangs without spitting out an error message first then it could be a bug

If you think you have found a bug in OINK, please send an email to the developers with info about the problem. Anything you can do to isolate the problem and reproduce it on a small data set will be helpful.

5.1 Error & warning messages

These are two alphabetic lists of the ERROR and WARNING messages OINK prints out and the reason why. If the explanation here is not sufficient, the documentation for the offending command may help. Grepping the source files for the text of the error message and staring at the source code and comments is also not a bad idea! Note that sometimes the same message can be printed from multiple places in the code.

Errors:

All universe/uloop variables must have same # of values

Self-explanatory.

All variables in next command must be same style

Self-explanatory.

Cannot attempt to open a 2nd input script, when the original file is still being processed.

Arccos of invalid value in variable formula

Argument of arccos() must be between -1 and 1.

Arcsin of invalid value in variable formula

Argument of arcsin() must be between -1 and 1.

Cannot open input script %s

Self-explanatory.

Cannot open log.oink

The default OINK log file cannot be opened. Check that the directory you are running in allows for files to be created.

Cannot open logfile %s

The OINK log file specified in the input script cannot be opened. Check that the path and name are correct.

Cannot open logfile

The OINK log file named in a command-line argument cannot be opened. Check that the path and name are correct.

Cannot open screen file

The screen file specified as a command-line argument cannot be opened. Check that the directory you are running in allows for files to be created.

Cannot open universe log file

For a multi-partition run, the master log file cannot be opened. Check that the directory you are running in allows for files to be created.

Cannot open universe screen file

For a multi-partition run, the master screen file cannot be opened. Check that the directory you are running in allows for files to be created.

Cannot redefine variable as a different style

An equal-style variable can be re-defined but only if it was originally an equal-style variable.

Command input is equal-style variable

Only variables that store strings can be used.

Command input variable is unknown

Self-explanatory.

Command outputs must be specified in pairs

Self-explanatory.

Could not create dir for file %s\n

Self-explanatory.

Could not open file in print

This comes from the output "print" routine of the neigh_tri command.

Could not open output file %s for output object()

Self-explanatory.

Divide by 0 in variable formula

Self-explanatory.

Expected floating point parameter in variable definition

The quantity being read is an integer on non-numeric value.

Expected integer parameter in variable definition

The quantity being read is a floating point or non-numeric value.

Failed to allocate %d bytes for array %s

Your OINK simulation has run out of memory. You need to run a smaller simulation or on more processors.

Failed to reallocate %d bytes for array %s

Your OINK simulation has run out of memory. You need to run a smaller simulation or on more processors.

ID in mr command is already in use

Self-explanatory.

Illegal ... command

Self-explanatory. Check the input script syntax and compare to the documentation for the command. You can use -echo screen as a command-line option when running OINK to see the offending line.

Input line too long after variable substitution

This is a hard (very large) limit defined in the input.cpp file.

Input line too long: %s

This is a hard (very large) limit defined in the input.cpp file.

Invalid Boolean syntax in if command

Self-explanatory.

Invalid named command switch

Only -i and -o are allowed.

Invalid command-line argument

One or more command-line arguments is invalid. Check the syntax of the command you are using to launch OINK.

Invalid keyword in variable formula

Self-explanatory.

Invalid math function in variable formula

Self-explanatory.

Invalid seed for Marsaglia random # generator

The initial seed for this random number generator must be a positive integer less than or equal to 900 million.

Invalid syntax in variable formula

Self-explanatory.

Invalid variable evaluation in variable formula

A variable used in a formula could not be evaluated.

Invalid variable in next command

Self-explanatory.

Invalid variable name in variable formula

Variable name is not recognized.

Invalid variable name

Variable name used in an input script line is invalid.

Invalid variable style with next command

Variable styles equal and world cannot be used in a next command.

Label wasn't found in input script

Self-explanatory.

Log of zero/negative value in variable formula

Self-explanatory.

MR ID must be alphanumeric or underscore characters

Self-explanatory.

MR object map command variable is unknown

Variable used as collection of strings is not recognized.

MR object add comand MR object does not exist

Second MR object is not recognized.

MR object command input is equal-style variable

Only variables that store strings can be used.

MR object created by copy already exists

This command creates a new MR object, which cannot already be defined.

MR object map command MR object does not exist

Second MR object is not recognized.

Mismatch in command inputs

Named command defines different number of inputs.

Mismatch in command outputs

Named command defines different number of outputs.

Must use -in switch with multiple partitions

A multi-partition simulation cannot read the input script from stdin. The -in command-line option must be used to specify a file.

Object input() invoked with invalid index

Index argument must be from 1 to Ninputs.

Object input() map function does not match input mode

Input command is used to select map mode (mmode) which much match map() function.

Object input() with no map function

Input script specified input from file, but no map() method was provided by named command.

Object output() as MR object not allowed

Input script speficied output as MR object, but named command invoked disallow flag.

Object output() called for unknown MR object

A MapReduce object unknown to the object manager was passed to the output() method by a named command.

Object output() invoked with invalid index

Index argument must be from 1 to Noutputs.

Object permanent() called for unknown MR object

A MapReduce object unknown to the object manager was passed to the permanent() method by a named command.

Ouptut MR ID must be alphanumeric or underscore characters

Self-explanatory.

Power by 0 in variable formula

Self-explanatory.

Processor partitions are inconsistent

The total number of processors in all partitions must match the number of processors LAMMPS is running on.

RMAT a,b,c,d must sum to 1

Self-explanatory.

RMAT fraction must be < 1

Self-explanatory.

Sqrt of negative value in variable formula

Self-explanatory.

Substitution for illegal variable

Input script line contained a variable that could not be substituted for.

Too many edges for one vertex in reduce first_degree

Number of edges of one vertex exceeds max integer in tri_find command. Will never be able to emit N^2 angles.

Tour + vertex reduce exceeds one block

No matching end double quote was found following a leading double quote.

Universe/uloop variable count < # of partitions

A universe or uloop style variable must specify a number of values >= to the number of processor partitions.

Unknown command: %s

The command is not known to OINK. Check the input script.

Variable name must be alphanumeric or underscore characters

Self-explanatory.

World variable count doesn't match # of partitions

A world-style variable must specify a number of values equal to the number of processor partitions.

Warnings:

Placeholder

No warnings are yet defined in OINK.