Frequently Asked Questions: Difference between revisions

From CIRPwiki
Jump to navigation Jump to search
No edit summary
No edit summary
Line 1: Line 1:
== Why can I not change the minutes in the starting time in the CMS-Flow? ==
== Why can I not change the minutes in the starting time in the CMS-Flow? ==
In SMS 10.1 the starting time in CMS-flow must start at hourly intervals and changing the minutes field is not allowed.
In SMS 10.1 the starting time in CMS-flow must start at hourly intervals and changing the minutes field is not allowed.
== Why can I not Hot Start the CMS-Flow V4.0? ==
Currently, the inline CMS V4.0 does not support hot starting. It does not output hotstart files nor can it read hotstart files. The feature is currently being tested and will be released in the near future.


== Why can I not run the implicit CMS in SMS? ==
== Why can I not run the implicit CMS in SMS? ==
Line 11: Line 14:


SMS 10.1 does not currently support the inline model, so it has to be run either using advanced cards or from the command prompt. For more information see ().
SMS 10.1 does not currently support the inline model, so it has to be run either using advanced cards or from the command prompt. For more information see ().
----

Revision as of 16:39, 19 May 2010

Why can I not change the minutes in the starting time in the CMS-Flow?

In SMS 10.1 the starting time in CMS-flow must start at hourly intervals and changing the minutes field is not allowed.

Why can I not Hot Start the CMS-Flow V4.0?

Currently, the inline CMS V4.0 does not support hot starting. It does not output hotstart files nor can it read hotstart files. The feature is currently being tested and will be released in the near future.

Why can I not run the implicit CMS in SMS?

The official release of CMS v3.75 only supports an explicit solution scheme. The new inline version of CMS v4.0 will support an implicit scheme and is being released as a beta version in May 2010. The inline CMS includes both CMS-Wave and CMS-Flow and performs the steering process internally without the interface. The advantages of the inline code are

  1. Efficiency gain by not having to initialize (file read, variable allocation, and calculation) CMS-Flow and CMS-Wave each steering run.
  2. Efficiency gain by saving interpolation coefficients between CMS-Flow and CMS-Wave in memory during steering run.
  3. Efficiency gain by not having
  4. No need for SMS so CMS can run on other platforms such as Linux.
  5. Option to pause runs.

SMS 10.1 does not currently support the inline model, so it has to be run either using advanced cards or from the command prompt. For more information see ().