[1846] in Enterprise Print Delivery Team
Filesizes for rip options
daemon@ATHENA.MIT.EDU (Lynne E. Durland)
Mon Oct 29 13:43:25 2001
Message-Id: <5.0.2.1.2.20011029133635.00af0ec0@hesiod>
Date: Mon, 29 Oct 2001 13:43:24 -0500
To: printdel@MIT.EDU
From: "Lynne E. Durland" <durland@MIT.EDU>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Greetings,
I have now had a chance to run some rips on the file Mark Prudden submitted
this morning.
The results were about what was expected.
The 240 dpi file was about 8 times larger than the original PS file.
The 300 dpi file was about 13.2 time larger than the original PS file.
The 600 dpi file filled the disk space where I was writing the test files
and so I have no data. (the 300 dpi file took up ~37% of the space)
In poking in the manuals I think I have figured out that if the resolution
is set to default for the logical destination/default document, then this
will pass the information to the transform to rip the file at 240 dpi. The
default behavior for the transform as currently configured is 300 dpi.
The printer is currently set to 240/600 dpi setting.
So I believe that the best course of action is for the production GL queue
be set to default, which is 240 dpi.
This will make our space calculations true and workable. Running at 600
would not leave us room for growth and could potentially fill the space we
have requested.
I will set the option in the logical destination tomorrow, that will give
y'all a chance to let me know if my thinking is bent or on the mark.
Lynne
Lynne E. Durland
Information Systems
Database Services
W91-109
O: 617-258-5857
C: 617-293-8091
H: KB1FEM
"When one door of happiness closes, another opens; but often we look so
long at the closed door that we do not see the one which has been opened
for us."
--Helen Keller
