General

InTime glossary

  • Recipe: A ready-to-use set of InTime Tcl commands. For more information see recipes.
  • Strategy: A set of settings and/or constraints generated for a design. An InTime recipe generates multiple strategies, then runs and analyzes each strategy’s results. Strategies are equivalent to a revision or a run in an FPGA project.
  • Revision: A reference to a strategy in an FPGA project. For example, in QuartusII, an InTime revision is the same as a normal QuartusII project revision.
  • Parent Revision: The topmost revision of a flow iteration / round. For more information see Parent Revision Properties.
  • Base Revision: The parent revision of a multi-round recipe. For more information see Parent Revision Properties.
  • Default Revision: The active revision / run in an FPGA project when it is opened in InTime. For more information see Parent Revision Properties.
  • Timing Score: A metric for the timing performance of a strategy; equivalent to the absolute value of the Total Negative Slack (TNS) across all paths (Setup, Hold, Recovery, Removal, Minimum Pulse Width). For more information see What does the Timing Score mean?.

What FPGA software are supported?

Check here to see the latest supported tools.

What information is submitted by the InTime crash reporter?

When something goes wrong in InTime or the InTime Agent, a crash report will automatically be created. The crash reporter sends the following files to Plunify in order to fix the problem:

  • Crash Report: A log which contains information about InTime’s internal state at the time the crash happened (this does not include personal information, but things like stack traces etc.)
  • Session Log: A record of the period when the crash occurred, so that the crash can be reproduced.

Why does InTime keep old session logs?

InTime keeps recent session logs in <home>/.plunify to allow the user to reference work done during those sessions. InTime automatically recycles these logs when they are older than 5 days, so it is not necessary to manually remove them.

How can I control the GUI language used?

By default InTime uses the language set in the system locale, but users can set a specific language using the -locale commandline argument.

<install directory>/intime.sh -locale <locale>

The following locales are currently supported:

  • English: en
  • Chinese (Simplified): zh_CN