Input and Output Files
This table shows file type combinations supported by DOcplexcloud:
Model type | Input file type |
Output file type |
Comments |
---|---|---|---|
CPLEX | .lp |
.xml |
The output format can be specified using the API. For DropSolve the output format is .xml only. |
CPO | .cpo |
.xml |
The output format can be specified using the API. For DropSolve the output format is .json only. |
OPL | .mod |
.xls |
In DropSolve, an .xls file is returned if at least one .xls is submitted, and a .json file is returned if at least one .json file is submitted. Using the API, .json is the default output format, you can specify .xls or .txt output format. |
DOcplex | .py *.* (input data) |
Any output file type, specified in the model | Python files are executed in a docker container running Anaconda 4.0 and Python 2.7. |
More Information
File name restrictions
DOcplexcloud has certain restrictions on file names. A file name
- is limited to 255 characters;
- can include only ASCII characters;
- cannot include the characters
/\?%*:|"<>
, the space character, or the null character; and - cannot include _ as the first character.
CPLEX file formats
The schemas for the CPLEX formats for solutions, conflicts, and feasibility files are available to download. Click here to download them in a .zip archive.
CPO file format
The native file format for CPO models is documented on the Knowledge Center: CP Optimizer file format syntax.