Project conversion

When you import a Classic Hull project, that is, an existing HDX project to COS or add it as a standalone project (local project), some conversions need to be done.

Important: The project administration must be upgraded in Hull versions from 2023T2 onwards. The project data is not affected, but the converted projects are not accessible anymore in Hull versions 2023T1Rx or earlier.

COS (distributed) projects

When you import an existing Hull HDX project to COS, the project is automatically copied. The copied project is then converted so that it can be used in the COS environment.

Important: All Hull users must exit the COS projects before project conversion, otherwise the project administration conversion fails. The failed conversion can be attempted to be corrected manually using the Hull COS Client Command Line Interface (HCC CLI). For more information on the recovery, see the Project Administration subcommands in Hull COS Client Command Line Interface (HCC CLI).

Note: When importing an existing Hull HDX project into a new COS project, save all blocks after the import, because they are not automatically saved. Save also all the blocks regularly.

During conversion, the information in var\seclist and norms\sectiongroup.dat are combined into ncgdb\projectinfo.xml. In addition, the files seclist, seclist.dat, and sectiongroup.dat are renamed to seclist.classic, seclist.dat.classic, and sectiongroup.dat.classic.

When the project is opened for the first time, some minor conversions take place at every site: if found, the GDL output parameter is removed from panel3d.conf, the gdl folder is removed from each block folder, and Outfitting holes are removed and flagged in each block. Saving the result requires a checkout of the relevant data. At the main site, users are reminded to save the updated norms as soon as possible.

During project conversion, a block is marked as created when the file <blockname>\db.cfg is present in the project folder. Otherwise, the block is marked as predefined.

For instructions on importing existing projects to COS, see Importing existing Hull projects to COS.

For more information on the new project administration files, see Hull administration files.

Standalone (local) projects

Note: Standalone (local) projects are automatically upgraded by opening them. COS (distributed) projects are upgraded when the COS/HCA server that manages them, is upgraded.

Important: After the conversions are done, you can no longer open the project in older (HDX) versions of Hull. Make sure to take backups of your projects before starting.

When you add an existing Hull HDX project as a standalone (local) project, you are asked to confirm the conversion. In order for the conversion to succeed, all project data must be available and users/processes cannot be active in the project.

After confirmation, the project is converted and available for use.

During conversion, the information in var\seclist and norms\sectiongroup.dat are combined into ncgdb\projectinfo.xml. In addition, the files seclist, seclist.dat and sectiongroup.dat are renamed to seclist.classic, seclist.dat.classic and sectiongroup.dat.classic.

During project conversion, a block is marked as created when the file <blockname>\db.cfg is present in the project folder. Otherwise, the block is marked as predefined.

For instructions on adding standalone (local) projects, see Importing existing standalone (local) projects.