Partial Loading of Model Files

Constraints

When you open a project where model files are set to be loaded manually, those model files will be in an unloaded state. The following features are constrained in this state, and their constraints are as follows:

Feature	Constraints
Search and Error Checking	Models included in unloaded model files are excluded. Regardless of the load setting, unloaded model files will not be loaded at runtime. The fact that there are excluded model files and the number of such files will be displayed, but it will not be possible to see how many models were excluded. To include them in the results, load the target model files and run again.
Trace Coverage	Models included in unloaded model files are also included in the calculation (because it is calculated based on whether or not there is a relationship).
Profile Editing	If there is even one unloaded model file, a message to that effect will be displayed and execution will not be possible. Click the number of unloaded model files displayed in the status bar to load them from the [Load Model File] dialog, or select the target model and load it before running. If background loading is not complete, a confirmation will appear asking if you want to load it immediately. Selecting [Yes] will load it and allow you to edit it.
Project Difference Comparison	Compares only loaded model files and displays this in the output window. Regardless of the load settings, unloaded model files will not be loaded for comparison. To include all files, load the model files beforehand before running.
Export Model File	All unloaded model files are loaded and processed at runtime.
Model File Integration	All unloaded model files are loaded and processed at runtime.

Notes on Displaying and Loading Manually Loaded Model Files

• To include unloaded model files in the search and error check results, load the target model files beforehand and run again.
  See the following for loading methods.

• Modeling > Team Development > Distributed Development with Teams > Partial Loading of Model Files

• Loading unloaded model files cannot be canceled midway.
  If you select another model during loading, the display of the previously selected model will be completed before the subsequent selection is processed.
  Large model files can be loaded in advance using the [Load Model Files] dialog or set to automatic loading and loaded in the background to avoid waiting time when selecting them.

• In projects with many model files set to manual loading, the names, hierarchies, and traces of those models will be displayed when the project is opened, increasing the time and memory usage when opening the project.
  Unloaded model files are loaded when needed, so in environments with limited memory, memory usage will increase as loading progresses, which may cause slow performance or memory shortage errors.

Notes on Opening a Project

• Functions that reference the entire project's models, such as search/replace, difference comparison, and error checking, will only be executed after the model files configured for automatic loading have finished loading.

• Profile editing can only be performed after all model files have finished loading.

If you attempt to edit a model file configured for automatic loading before it has finished loading, you will be notified that it is still loading and that editing will be possible after completion.

Even if some model files fail to load, you can reload the remaining model files and edit them without reopening the project.

Partial Load Nodes and Notes

If a model's parent is included in an unloaded model file and does not exist in the Model Navigator, a node labeled [Partial Load] will appear at the bottom of the Model Navigator. Below it, the unloaded model and its submodels will be displayed. These nodes are called Partial Load Nodes.

By selecting a model under a partial load node and clicking "Load Parent Model" from the context menu, you can load all model files, including the ancestor models of that model, in one go.

Restricted Functionality

Even if you specify the entire project as the scope for the following functions, models corresponding to partial load nodes will be excluded:

• Search
• Error Checking
• Document Output

Model Path

At the top of the Next Design editor, there is a path bar that displays the model's path. Normally, the path bar displays the absolute path from the project root, but please note that a different path is displayed for models displayed under partial load nodes.

• Models displayed under partial load nodes have ":partial" appended to the beginning of their path.

• When the loading status of model files changes, they move from under the partial load node and the path changes.

User Settings Memory and Notes for Projects

Partial load settings are stored in the {project file name}.nuser file located in the same folder as the project file.

When using a configuration management system, please note the following regarding the handling of .nuser files:

Note that understanding the aforementioned constraints is necessary when using partial loading. Therefore, if you are sharing .nuser files with all team members, we recommend that you ensure everyone is aware of these constraints beforehand.

Notes on Subversion

• When registering a project to a repository in Next Design, .nuser files are excluded from configuration management.
• If you want to manage .nuser files using configuration management, please register and commit them manually using a tool other than Next Design.
• Even if .nuser files are changed, they will not appear in the list of commit targets in Next Design.

Notes on Git

• Unless you are sharing partial loading settings with all team members, please add .nuser files to your .gitignore file to exclude them from configuration management.

General Notes

• Unloaded model files are not subject to error checking, etc. Please load the model files you want to target before running the program.

• If you are not using configuration management for .nuser files, and someone else changes the hierarchy or name of a model file that you have set to load manually, the manual load setting will be invalidated because the path will not be updated.