Bladed versions affected: 4.4 and older
Date of last article update: 4th January 2024
=========================================================================
Batch jobs created in Bladed 4.4 (or older) are added to the internal batching tool within Bladed, and not to Batch 1.6.
The Batch Migration Tool can be used to convert a batch list created in Bladed 4.4 or older to the new jobs list format that can be opened in the newer version of the Batch tool (the current version of the Batch client is version 1.6, which is distributed with the most recent versions of Bladed).
The tool can be used from the command line, and has the following format for a simple migration use case:
BatchMigrationTool.exe -s “[full path to old style batch folder]” -e "[full path to dtbladed executable to use]" -m
A summary of all of the available command line options can be obtained by running:
BatchMigrationTool.exe --help
To migrate a batch list, please use the following procedure:
- Make sure that the (new) Batch client is running.
- Open a command prompt window.
- Navigate to the Batch tool program folder (e.g. C:\Program Files (x86)\DNV\Batch 1.6) in the command prompt window.
- Run the migration tool command, including the relevant paths, e.g.
BatchMigrationTool.exe -s “C:\Program Files (x86)\Bladed 4.3\batch” -e "C:\Program Files (x86)\Bladed 4.3\dtbladed.exe" -m
- Confirm the warning prompt that appears.
- The batch list should appear on the Jobs List tab in the Batch client. Note that the list will be migrated to a list with the same name as the sub-folder containing the old batch list (e.g. “batch” in the above example) - if a new batch list already exists with this name, the jobs will be added to this existing list, otherwise a new batch list will be created.
Notes:
- If the batch list folder is nested (i.e. it contains folders that are themselves batch lists), you could add the –r switch to the command to do a recursive upgrade which will process subfolders of the folder specified by the –s option.
- Note that you can only specify a single executable for the conversion. If you have multiple folders within your main batch-list that contain jobs for different calculations (e.g. loads calcs that use dtbladed and post processing calcs that use dtsignal), you will then need to process these folders separately, specify the paths to the appropriate executables.
- The migration process will point the new jobs to produce results in the same output folders as the original old style batch jobs. These output folders will be cleared as part of the upgrade. So, if you want to keep results from any previous runs, you will need to back those up before going ahead with the run.
It is advisable to first try out the migration tool using some dummy jobs to get used to how the tool works, before migrating any real jobs.