Appendix C: FAQs for meiConfig and meiConfigGui

Why are some floating point numbers displayed as 1.#QNAN or -1.#QNAN?

For floating point numbers, there are certain bit patterns that are not valid numbers, known as NaN, or "Not a Number." In the case of a union with a float member and a long member, the float member will sometimes have an NaN value. For example, it will have a value of -1.#QNAN if the long member is -13107. The Q stands for "Quiet," or do not raise an exception. Other seemingly strange values for a floating point number are 1.#INF and -1.#INF (infinity and negative infinity). These values do not cause a problem for meiConfig because for unions with a float member and a long member, only the long member is actually used when restoring the value.

Why is MPISynqNetPacketCfg excluded in the default filter file?

The MPISynqNetPacketCfg structure is saved to the controller using the mpiSynqNetPacketConfigSet(...) function. Since this function reinitializes the network, it can take a long time for completion. Also, including the MPISynqNetPacketCfg structure can significantly increase the size of the configuration file for large networks. Most users will not change the packet configuration, so it is normally excluded for optimization purposes.

I'm trying to include/exclude an individual element in a filter file, but meiConfig displays the error message "Failed to parse the filter file."

The ability to include and exclude individual elements in a list of elements was added to meiConfig version 03.02.02. Prior to this version, individual elements could not be specified.