Developement Of A Batch Mode For Conduit And Its ... - Cal Poly
Developement Of A Batch Mode For Conduit And Its ... - Cal Poly
Developement Of A Batch Mode For Conduit And Its ... - Cal Poly
You also want an ePaper? Increase the reach of your titles
YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.
eing opened by a regular session of CONDUIT. The running and saving of the problem<br />
would be done in the same way as in CONDUIT.<br />
Each method has its benefits and deficiencies. The first method would take up<br />
less disk space, however the running and saving of the problem would be more complex.<br />
Conversely, the second method would require much more disk space, the amount<br />
depending on the number of cases. A typical CONDUIT problem might take up 1-2<br />
megabytes of disk space after the results have been saved. Even with a large number of<br />
cases, however, the amount of space needed is still reasonable, considering the size of<br />
modern hard drives.<br />
Saving multiple CONDUIT problems would have many more advantages, though.<br />
The organization of the cases is much clearer, and the components of the individual cases<br />
can be seen by simply viewing the <strong>Batch</strong> Problem directory. Furthermore, by using this<br />
method, the running of the cases would be greatly simplified, as the code need only to<br />
switch to a particular directory and use the run code already developed for CONDUIT.<br />
Finally, the second method is more versatile in that many of the functions of <strong>Batch</strong> <strong>Mode</strong><br />
can be performed by hand. The user may open and run the individual cases using<br />
CONDUIT, delete cases by deleting their respective subdirectories, or create new cases<br />
by copying a case subdirectory and its contents to a new subdirectory.<br />
32