User Area > Advice
Using networks & file corruption
Working on LUSAS models which are stored on a network
drive is NOT recommended. Modelling and solving over a network
connection is in general:
-
far slower than solving locally (being dependant on
network traffic)
-
more susceptible to writing
errors, which may result
in file corruption and LOSS OF WORK (Modeller)
-
more susceptible to writing errors, which may result
in wasted analysis time (Solver)
The network connection may be interrupted
because of extended period of inactivity across the mapped
drive connection. This can occur for relatively large analyses
in which there is a long period between each stage of the
analysis. In
addition, there may be a disk space limit on your network folder (imposed
by an administrator) which can lead to difficulties storing or solving
models. For the same reasons, LUSAS temporary files
should not
generally be directed to network areas.
Model
files (*.MDL) are binary and therefore quite large.
They are opened quickly by LUSAS Modeller, but can be susceptible
to corruption. There is
unfortunately little that can be done to salvage a corrupted binary file
and so it is essential to keep backups. Results
files (*.MYS) are also binary and are normally larger than your model
file. Storing results files
can use up valuable network/ archive space.
A results file can always be re-created from a model file, and a
model file can be re-created from a command file. Command files
(*.CMD) are ASCII and are much smaller than
Model files, making them easier to store and less susceptible to
corruption.
|
