oSP3D cannot create an optiSLang binary file from start to finish. It can only modify an existing file, basically creating a modified copy of the original file. This is necessary to keep information on the parameter definitions of optiSLang. You can use the exported binary file directly in optiSLang's MOP solver. When modifying the file, all defined responses are replaced by the parameters to be exported from oSP3D.

If any data is already imported from optiSLang, oSP3D tests the equivalence of the already imported file and the optiSLang binary file that serves as a reference for export. This step may be necessary to ensure data consistency of two independent samplings.

If a scalar data object to be exported contains a missing data item, the value is marked as NaN in the output file. optiSLang's MOP solver then ignores the specific value in the analysis.