What's new

Frequently asked questions:

Is Dragon Version4 an official version? What is its status relative to Dragon 3.0x?

Dragon 3.0x releases are intended to be Industrial Standard Toolset (IST) components for the Canadian nuclear industry. They are used for design and safety studies. Consequently, IST components are verified according to the procedures described in CSA-N286.7. Some modules of Dragon Version4, such as NXT:, LIB:, EVO: and SHI: are common with Dragon 3.0x and are therefore fully verified. Other modules of Dragon Version4, such as FLU: and EDI:, have been completely rewritten and are not verified according to CSA-N286.7.

However, the development of Dragon Version4 is made with modern quality assurance (QA) traceability techniques. This traceability goal is achieved through the application of versioning control (using Subversion) and issue tracking systems to the following project components:

Fortran sources of the Version4 components
Non-regression tests
Software documentation
Scripts of the NJOY-based library production system

Can I use my Dragon 3.0x input files with Dragon Version4?

Yes, with one exception. Version4 has eliminated all side effects. In Dragon 3.0x, it is usual to use a side effect in module UTL: to change the root directory in a LCM object. In Version4, this operation must be accomplished with the equality (:=) module, as shown in the following example.

In Dragon 3.0x:
LINK_LIST LIBRARY TRACK GEOM ; ... UTL: LIBRARY :: STEP UP MACROLIB ; TRACK := BIVACA: GEOM LIBRARY ; UTL: LIBRARY :: STEP DOWN ;

In Dragon Version4:
LINK_LIST MACRO LIBRARY TRACK GEOM ; ... MACRO := LIBRARY :: STEP UP MACROLIB ; TRACK := BIVACA: GEOM MACRO ;

Also, a few modules, such as CFC:, JPMT:, SAD:, PER: and MCU: are not available in Dragon Version4. The capabilities of modules EXCELL: and MOCC: have been integrated in ASM: and FLU:, respectively.

Can I use my Donjon 3.0x input files with Donjon Version4?

No, although Trivac-related modules have similar arguments. All modules related to L_MAP and L_DEVICE objects are different. Objects L_TABLE no longer exist in Donjon4. L_COMPO and L_MULTICOMPO objects are interpolated in place in Donjon4, without having to first copy them in a L_TABLE object. The programmation of Donjon4 is greatly simplified and cleaned.

Is Dragon Version4 works on Windows?

Yes, in two possible ways:

A native build is possible, provided that Microsoft Visual Studio and Intel Visual Fortran are available. A script named instver4.bat is available as of Version 4.0.4 to create executables (.exe) from a MS-DOS command window. Follow the following steps:
- Click Start, point to All Programs, Intel(R) Software Development Tools, Intel(R) Visual Fortran Compiler Professional and finally Fortran Build Environment for applications running on IA-32. The Visual Studio Command Prompt automatically sets the correct paths of both C and Fortran compilers, together with their associated libraries.
- In the command window, type
  cd %homepath%\Version4\
  .\script\instver4
A "Unix-type" build is possible, provided that Cygwin is properly installed on your PC. Cygwin is a native implementation of a Unix shell. After installation of Cygwin, you obtain a native Unix terminal window where all Version4 components can be executed.

Is Dragon Version4 works on Mac OSX?

Yes. Many components of Version4 are developed on a Mac. However, you must install XCODE and the g77 Fortran compiler before installing Version4. The gfortran compiler is supported as of Version 4.0.2.

A tutorial is available to explain the installation procedure on a Mac.

Why using Fortran 77?

We are using Fortran 77 for performance and serviceability reasons. The style of Fortran programming we use is nevertheless modern as we don't use obsolete constructs such as COMMON blocks for static storage needs. We keep the possibility to convert our Fortran code easily toward Fortran 2003 by replacing the CALL SETARA() and CALL RLSARA() constructs with ALLOCATE and DEALLOCATE statements in a relatively automatic way. This operation is planned for the Version5 disribution, using the architecture presented in report IGE-313 (PDF).

Can I use Version4 components for commercial applications? What are the terms of the license?

The Version4 components are released under the GNU Lesser General Public License (LGPL). This means that you can integrate Version4 components into your industrial framework and use it for commercial applications. The only condition is to inform and make available to us any modification or improvement you make in an existing Version4 component.

Enhancements to Version4 can be written as procedure files in CLE-2000 language or as modifications to the Fortran source. CLE-2000 procedures or new Fortran modules written by you are not covered by the LGPL. We encourage you to release your Fortran source enhancements under the LGPL for inclusion in future versions of Version4.

Why not giving full remote access to the Subversion repository?

Because the Subversion repository contains few components that are not open source, such as the Njoy 99.0 Fortran source and the NDAS access routines used to access proprietary libraries from Atomic Energy of Canada Limited (AECL). These components are not available on the Web downloads.

Which cross-section libraries can I use with Dragon Version4?

You can use existing libraries in the following formats: MATXS, Apolib-1, Apolib-2, WIMS-D4, WIMS-AECL and Draglib. Most available libraries in these formats are proprietary, but open source libraries exist in WIMS-D4 (see WLUP site) and Draglib formats.