#Indiv. Log files
10 messages in this thread
Brian,
A very nice and what would seem to be a very simple capability to add. It
would be nice to have an option for each network node to create and update its
own LOG file in addition to the group log file that is created. This would
allow a very quick and simple method of adding up machine hours for rendering
jobs/services .. thus allowing for accurate billing record to clients for
rendering time. The problem with only having the one LOG .. with having
machines comming on and off line at different times of the day .. and machines
occasionaly failing .. its nearly imposible to pull that info out.
A secondary option for implementing this same capability .. but may even be
easier and certianly even more flexible.. would be to use a standard "database"
structure for the LOG file information instead of "free-form" text streaming
that you are currently using. If the log file was in a form that could be
easily imported into a database program as a table or an Excel .XLS .. or
something, the user could easily "sort" the information how ever is best for
them .. by project, by machine, by time, by error code, etc….
This is something that my clients are really interested in.
Ang
Angelo,
<< network log ideas.. >>
Gary has stated that he would free some of his programmer's up to document the
MCS data structures *if* someone committed to a worth while project. It sounds
that you have a very good idea of what you'd like and your comments constitutes
the *start* of a worth while project description.
Everyone please add you ideas to how Network rendering could be extended to
this thread.
jonas[adesk]
Hi Jonas,
I have a couple of ideas regarding the MCS system for 3DS.
1) Create a DOS command line method of adding, editting and reviewing the MCS
without having to tie up one of the computers that is currently running 3DS. In
other words, when all of the machines in our office are rendering a project
(including the master machine with HW lock), we can't monitor the MCS or make
adjustments to the MCS (i.e. "clean") without cancelling the rendering process
of one of working machines. I'd like to be able to control the MCS from a
computer that is otherwise not capable of running 3DS, i.e. old 286's or
low-memory 386's. And on multi-tasking OS's like OS/2 an operator could
probably have 3DS rendering in the background and still make adjustments to the
MCS through another DOS box.
2) By developing a DOS method of manipulating the MCS, it would make it
possible to monitor and add projects to the MCS at the office, while dialing in
to the network via modem from home <G>! For example, in our office we run a
Lantastic network where one of the computers operates as a BBS. I am currently
able to dial into our BBS and do a remote shell to DOS. From there, I can log
into our MCS control directory and "view" the ?????.log files to evaluate the
progress of the machines. This can tell me when the machines will complete a
particular job.
The bonus side of this would be to upload a new project to the BBS (that I've
completed at home) and place it in the MCS control directory, then run a DOS
MCS control program to add the project the MCS and have the office machines
"pick up" the new job. That way operators could control the 3DS slaves at the
office over an entire week-end without having to leave home <G>!
3) I'd like to be able to see the MCS control rendering of specific frame
numbers from an ASCII file list (kind of like an .IFL). For example, perhaps
you would like to render frames 1 – 150 and 180-240 in the same project.
Currently you have to prepare two net queue rendering jobs, one covering the
first range and another covering the second range. The problem with this is
that slave machines must load the same project twice to participate with both
rendering tasks (wasting precious memory).
Memory efficiency would be achieved by allowing a "frame list" file that lists
the specific frame numbers that should be rendered, without having to reload
the project. The "frame list" file might have a format like this:
1-150×2 (render frames 1 thru 150 by 2) 155 (render single
frames) 159 160-185×1 (render frames 160 thru 185 by 1) etc.
Well, those are a couple of ideas I have for now. Any comments??
Later,
-Jeff
Jeff,
<< Any comments?? >>
Thanks.. Good ideas!. A programmer would have to describe the project to Gary
and commit to finishing it before Gary would free up any of his resources.
jonas[adesk]
Ang:
>> …would be to use a standard "database" structure for the LOG file
>> information instead of "free-form" text streaming…
Uh, Ang, I hate to mention the obvious, <g> but have you ever turned on the
"NET-DAT-FILE=YES" setting in the 3DSNET.SET file? It creates a network
database file ( *.DAT) for every project rendered, set up in a very pretty SDL
format for reading into a spreadsheet or word processor.
Just a thought,
Greg Pyros
Greg,
>> "NET-DAT-FILE=YES" setting in the 3DSNET.SET file?<<
Great! … I give it a try. Who said you can't teach an old dog new tricks <G>
Ang
Ang:
Just make sure to set it to "YES" on all your machines!
Greg Pyros
Greg,
It works perfect .. just what I was looking for.
Thanks .. Ang
Ang:
Any time I can help out a dealer in distress, I'd be glad to! :^)
Greg Pyros
Ang,
The .DAT files that are created can very easily break down the log information
in to what you are looking for. I bring them into Excel with no problem, and
then juggle the numbers in there.
-Brian