3.2     Batch operation with exported tasker files

A tasker file analogous to the one discussed in Batch operation with user tasker files is exported automatically by QW‑Editor, with appropriate setting of Tasker times in File-Export Options-Allow BHM-Details... dialogue. Fig. 3.2-1 shows the settings used in heat_auto.pro, which differs from heat.pro by these settings only.

Note that QW-Editor accepts integer number of periods, and hence the FDTD iteration numbers applied in heat_br.ta3 of Batch operation with user tasker files will be reproduced approximately (4995, 489 and 1958 in place of 5000, 500, 2000).

Also, the temperature patterns after consecutive BHM steps are saved in consecutive files with default name heat_auto1.vi3, heat_auto3.vi3 etc. Thus before re-running the QW-BHM for the same example (of the same name heat_auto.pro), either move the example to a new directory, or secure the *.vi3 files in another directory, as they will otherwise be overwritten.

Fig. 3.2-1 Heating Details dialogue for heat_auto.pro example.

Fig. 3.2-2 Temperature evolution in heat_auto project, and final temperature pattern across the load (in -20÷0°C scale).

Fig. 3.2-2 summarises the evolution of minimum and maximum temperatures in the load during the execution of heat_auto.ta3 (as read in the Log Output tab of the Simulator Log window). It also shows the final temperature pattern across the load (layer 8) in -20÷0°C scale. It excellently compares with Fig. 3.1-5 for heat_br.ta3. The differences in temperature levels are within 0.03°C, and only at the BHM iteration across the phase change they reach 0.1°C. This confirms that minor differences in the number of FDTD iterations at each BHM iteration do not influence the results.

More advance tasker files controlling load rotation, heat flow and tuning of the source are discussed in consecutive sections of this manual.