Minolta 5400: The classic (mostly green) lines

  • Thread starter Thread starter Markus Malmqvist
  • Start date Start date
M

Markus Malmqvist

Hi,

I guess this is a known issue, so feel free to point me to the definite
source of information, if such source exists.

For several weeks I have been trying to reach a Minolta support
organization that would know about this problem. I would like to know, if my
unit is within specs or not.

- there are about 20-30 horizontal lines of varying brightness, all color
channels represented, green most visible
- the lines are worst in very long dark slide scans (can be for example +50
units in 8-bit color channel)
- there are no slines in the left side of the scan, they gradually appear
when going towards right side
- the lines are always in the same place
- sometimes when using multisampling (4x) I do not get any lines even though
the scan time is long

-> it seems to me, that lines are caused by individual stuck CCD color
pixels, which are not properly reset between
scan columns, and thus erronous base charge starts to accumulate into
the pixels, this would seem to be a quality
control issue

A web search indicates, that the issue is recognized by the users, service
may not correct anything, and even if you receive a new scanner it may very
well have the same problem.

Since a Photoshop action can be used to interpolate the lines away, I would
probably accept the device, if the behavior is fairly typical, and service
is not likely to improve performance.

--markus
 
- there are about 20-30 horizontal lines of varying brightness, all color
channels represented, green most visible
- the lines are worst in very long dark slide scans (can be for example +50
units in 8-bit color channel)
- there are no slines in the left side of the scan, they gradually appear
when going towards right side
- the lines are always in the same place
- sometimes when using multisampling (4x) I do not get any lines even though
the scan time is long

-> it seems to me, that lines are caused by individual stuck CCD color
pixels, which are not properly reset between

The problems lies within the calibration routines: no CCD sensor has
all identical photodiodes, so a calibration step is done to equalize
their behaviour.
In earlier versions of both the Minolta Scan Utility and the 5400
firmware, the calibration routines leaved someting to be desired :) .
Try downloading and installing the latest software (v1.1.5) from the
Konica-Minolta web site.
It will also install a new firmware (v1.10) into your scanner, and the
streaks should go away (maybe you could still notice some very, very
faint lines in the shadows at high magnification when pulling the
exposure, but they will be very hard to notice).
Since a Photoshop action can be used to interpolate the lines away,

I won't suggest it: you'd end up loosing some details.
Should your scanner still show visible streaks after the software
upgrade, it means it's outside the norm, and, in my opinion, should be
replaced.

BTW, Minolta service does not have a clue... :(

Fernando
 
Hi,

I guess this is a known issue, so feel free to point me to the definite
source of information, if such source exists.
A web search indicates, that the issue is recognized by the users, service
may not correct anything, and even if you receive a new scanner it may very
well have the same problem.

If it's the known Minolta problem which was caused bin early driver
releases, then all you need to do is update the driver and firmware.
If it's this and the firmware/driver upgrade doesn't work then you
need to return the scanner.

The only other cause of lines across a scan with a Minolta is using
Vuescan.
 
Fernando said:
The problems lies within the calibration routines: no CCD sensor has
all identical photodiodes, so a calibration step is done to equalize
their behaviour.

I thought it would be something like that. The error seems to accumulate,
since the lines gain strength from left to right.

....
It will also install a new firmware (v1.10) into your scanner, and the
streaks should go away (maybe you could still notice some very, very
faint lines in the shadows at high magnification when pulling the
exposure, but they will be very hard to notice).

Unfortunately I already have all the newest software. The lines are only a
problem in long >30min dark slide scans with very long exposure.
I won't suggest it: you'd end up loosing some details.

Yeah, in theory. But who is able to see 30 interpolated lines from 5300
lines? It is hard to see them even in 100% view after interpolation.
BTW, Minolta service does not have a clue... :(

Yes, I have noticed that too... I guess they would know these issues in the
actual service place, which I believe is in Germany, at least for north
Europe. Unfortunately I have heard, that getting a Minolta scanner replaced
here in Finland can be next to impossible.

--markus
 
I thought it would be something like that. The error seems to accumulate,
since the lines gain strength from left to right.

Mmmh, so it's heavily related to heat accumulation and thermal noise.
In my experience (no longer than 5-6 mins scans) the lines appear to
be of more or less constant intensity throughout the scan, but on 30
mins scans I can imagine the problem gets worse.
Unfortunately I already have all the newest software. The lines are only a
problem in long >30min dark slide scans with very long exposure.

I'm working on a dark frame subtraction routine for Vuescan, after a
useful suggestion by Kennedy McEwen.
It's not a cure, just a patch, and a cumbersome patch at that (it will
require a dark frame scan with the same exposure setting, and will
require working with RAW scans and then re-acquiring them in Vuescan
with "scan from file"), but maybe it could help your cause; even if I
doubt I will find a way to compensate for the growing intensity of the
lines across the scan... I have to use a median value because I have
to average the random noise across the scan before trying the frame
subtraction.
Having done some very quick test, it seems to me that a d.f.s. routine
an also help with a too-high blackpoint I'm seeing in Vuescan scans.

I'm waiting for a fix on a ImageMagick bug I discovered (I'm using the
ImageMagick libraries to read and write TIFF files), but I hope they
will go after it shortly.

Please follow the thread "Vuescan Dark Frame Subtraction" for details
and news. The utility will be of course free and open source; I hope
to have early alpha-stage binaries for Windows, Linux and MacOS X in a
couple days, that is if the ImageMagick bug will be fixed.

Bye!

Fernando
 
Then writes...
The error seems to accumulate,
since the lines gain strength from left to right.
Then writes...
The lines are only a
problem in long >30min dark slide scans with very long exposure.

Sorry for hacking your quotes about Markus, but when these three
statements are presented together the problem you are reporting comes
into perspective.

I do not believe that you have a faulty Minolta scanner, so I do not
believe that replacing the scanner will eliminate this problem. In
fact, I would hazard the view that every user of the Minolta (and most,
but perhaps not all, other desktop film scanners) will experience
similar problems under these conditions.

As Fernando explained, each cell in the CCD has a unique dark current,
which is the current that flows into the storage well even when no light
is present. When the CCD is illuminated by an image, the photocurrent
generated by each cell flows into the storage well together with this
dark current. The resultant total charge packet accumulated in each
storage well is then transported to the device output, where it is
dumped onto a small capacitor to produce an output voltage sequence
proportional to the total packet of charge accumulated at each cell
during the exposure.

This raw voltage sequence, once digitized, would produce a very poor
image indeed, since the lowest levels would be determined by the dark
currents in the cells, whilst the contrast would be determined by the
photoresponse, which is also unique to each cell. Consequently the
scanner goes through a calibration step, as Fernando described, to
determine how the CCD responds to no light (measuring the dark current
in each cell) and full light (the difference between this and the no
light condition being a measure of the photoresponse). This data is
then used to compute a clean image from the raw data.

However, there are a couple of problems that arise.
1. The "calibration" is only accurate for the particular exposure used.
2. The dark current is a strong function of the CCD temperature.
There are other problems, such as the stability of the dark current,
even under a controlled, fixed temperature - so called 1/f noise, but we
can ignore these for the moment, since you are reporting something that
appears to be driven by these first two problems.

So far as problem 1 is concerned, the question is what exposure is used
in the calibration stage, and is it the same as the long exposure used
with the very dark slides you are experiencing the problem with? I
suspect it isn't - and consequently under these dark slide conditions,
the dark calibration is probably in error.

I don't have a Minolta scanner so I can't try this, but in another
thread Bart mentioned that you can force a calibration by using
Ctrl-Shift-I, to re-initialise the scanner. It may be possible, you
will have to check, to lock the exposure to that required for your dark
scans by auto-exposing on them first and then switching off the
autoexposure function. Re-initialising the scanner *may* then perform a
calibration with the same exposure as you are using for the scan and
thus create a more accurate dark current calibration reference.

I emphasise that I don't have a Minolta to try this with and frankly,
while worth trying, it really is grasping at straws! This is because
the calibration sequence also includes a response measurement, which
requires an exposure with the scanner illumination source on. With a
long exposure, this is likely to saturate the CCD. The Minolta, like
many other scanners, uses a cold cathode light source and this cannot
switch on an off fast enough (ie. in less time than the actual exposure
itself) to prevent saturation with long exposures.

It is one of the advantages of the Nikon series (and the newly announced
Mk-II Minolta) that they use LED light sources, which can be switched
very fast indeed, so such calibration under representative exposure
conditions is possible. I wouldn't like to suggest that this is why
Minolta have changed to an LED source on the new scanner, but it may be
a contributory factor.

So the best solution may actually be to lock the exposure with a normal,
*light* slide in place and then use that exposure to scan the dark slide
- correcting the density afterwards in the digital image, with all that
this entails in terms of increased noise etc.

So far as the second problem is concerned, I suspect that this is why
the intensity of your lines change across the image - 30 minutes is a
very long scan time to keep the CCD temperature stable! In a
professional imaging system, the CCD would be mounted on a
thermo-electric cooler, typically a Peltier device, not only reducing
the dark current dramatically but, using a very precise control system
to maintain the device temperature over long exposures, stabilising the
dark current. None of the desktop film scanners on the market have such
devices though, and rely on the device temperature remaining stable.

Roughly speaking, the dark current in a CCD cell increases by about a
factor of 2 every 7 or 8 degrees Celsius, so it doesn't take much
temperature change on the CCD to cause a significant change in dark
current. Fortunately, dark current is generally quite low in normal
usage and its change with temperature isn't too much of a problem during
the scan time. However, in dark scans with long exposure, it
contributes a much greater proportion to the total charge packet than it
would in normal use, so the change in dark current as a result of device
temperature change are consequently more significant also.

Since we are talking about device temperature here, rather than package
or case temperature, the main cause of temperature change during the
scan time is actually the power dissipation of the CCD itself. Usually,
the change in temperature is limited by operating the CCD for a couple
of seconds prior to beginning the actual scan, however this may not be
adequate for long exposure runs. So one suggestion to minimise the
problem, although you are unlikely to eliminate it entirely, is to start
a scan and let it run for, say, 5 minutes or so, then cancel and
immediately restart the scan. This may help to get stabilise the CCD
temperature better than the few seconds that the scanner uses for normal
exposures.

Summing up then, there are a couple of things you can try to alleviate
the problem, but very little that will eliminate it. I suspect you are
pushing the device quite a lot beyond its original design envelope. Not
much help in resolving your problem other than perhaps understanding the
issues better, which may lead you to avoid the situation in future.
 
Kennedy McEwen said:
I do not believe that you have a faulty Minolta scanner, so I do not
believe that replacing the scanner will eliminate this problem. In fact,
I would hazard the view that every user of the Minolta (and most, but
perhaps not all, other desktop film scanners) will experience similar
problems under these conditions.

Good, this is just what I was searching for, a feature explanation. :-) I
just thought that a 50 unit (8-bit) error in a color channel was a bit too
much... But if it can be understood as you explain, OK. I have to remember,
that only about 0.5% of lines and 0.2% of CCD color elements have this
problem.

....
However, there are a couple of problems that arise.
1. The "calibration" is only accurate for the particular exposure used.
2. The dark current is a strong function of the CCD temperature.
There are other problems, such as the stability of the dark current, even
under a controlled, fixed temperature - so called 1/f noise, but we can
ignore these for the moment, since you are reporting something that
appears to be driven by these first two problems. ....
I don't have a Minolta scanner so I can't try this, but in another thread
Bart mentioned that you can force a calibration by using Ctrl-Shift-I, to
re-initialise the scanner. It may be possible, you will have to check, to
lock the exposure to that required for your dark scans by auto-exposing on
them first and then switching off the autoexposure function.
Re-initialising the scanner *may* then perform a calibration with the same
exposure as you are using for the scan and thus create a more accurate
dark current calibration reference.

I will have to try that. It is also interesting, that I have a few 4x
multisampled long scans which are VERY clean indeed. But not all of them...
It just may be possible, that I would have manually calibrated the device
for some reason. It is also true, that the unit often does many automatic
calibrations during first few scans after switching the unit on. After that
it never automatically calibrates.

I guess the grain diffuser complicates dark current issue, since it greatly
reduces light accumulation per time unit?
So the best solution may actually be to lock the exposure with a normal,
*light* slide in place and then use that exposure to scan the dark slide -
correcting the density afterwards in the digital image, with all that this
entails in terms of increased noise etc.

With Minolta software it is possible to adjust exposure based on a
"standard" exposure, you just turn off the autoexposure. With prescan it is
easy to adjust exposure so that the result is dark, but hopefully has enough
information.

I guess I have to try this instead of maximizing the signal to noise ratio,
which of course was my perhaps naive objective.

....
adequate for long exposure runs. So one suggestion to minimise the
problem, although you are unlikely to eliminate it entirely, is to start a
scan and let it run for, say, 5 minutes or so, then cancel and immediately
restart the scan. This may help to get stabilise the CCD temperature
better than the few seconds that the scanner uses for normal exposures.

I guess that the temperatures are so high, that even moving the film,
autofocusing and starting the next scan of a batch will considerably lower
the temperature? Otherwise one would think, that the phenomenon would arise
less in the later scans of a batch. I am not sure, perhaps it does...
Summing up then, there are a couple of things you can try to alleviate the
problem, but very little that will eliminate it. I suspect you are
pushing the device quite a lot beyond its original design envelope. Not
much help in resolving your problem other than perhaps understanding the
issues better, which may lead you to avoid the situation in future.

Yes, thank you very much! This is the kind of answer I have been searching
for during the last almost four weeks. Of course, I was dum enough not to
try this newsgroup until few days ago...

--markus
 
On Sun, 6 Mar 2005 00:47:42 +0000, Kennedy McEwen

[snip]
However, there are a couple of problems that arise.
1. The "calibration" is only accurate for the particular exposure used.
2. The dark current is a strong function of the CCD temperature.
[snip]

So far as problem 1 is concerned, the question is what exposure is used
in the calibration stage, and is it the same as the long exposure used
with the very dark slides you are experiencing the problem with? I
suspect it isn't - and consequently under these dark slide conditions,
the dark calibration is probably in error.

I also thought the black readings would change but I did some testing on
my FS4000US recently and the difference was insignificant. The FS4000
has a 'speed' setting which ranges from 1 to 12 and seems to be a
divisor for the clock. Each shutter also has a 'duty-cycle' setting
which can range from 1 to 1000 (.1 - 100%). Both of these controls seem
to be linear.

For testing I had the lamp off and no film holder in the scanner. I
found the black readings increased significantly when the duty-cycle was
above about 90%. When the duty-cycle was 85% or less I found very
little difference even when the speed was varied from 1 (fastest) to 12
(slowest). All across the range (speed 1, duty .1% to speed 12, duty
85%) the readings were similar.

Testing with the lamp on and with a film holder in the scanner did
produce variations in the black level readings. The differences were
greater with the negative holder presumably because the black test bar
is narrower than in the slide holder.

Based on this testing I decided to use the black readings at the default
speed for all exposures. Do you think my testing is flawed ?

-- Steven
 
Steven said:
I also thought the black readings would change but I did some testing on
my FS4000US recently and the difference was insignificant.

Test details snipped for brevity.
Based on this testing I decided to use the black readings at the default
speed for all exposures. Do you think my testing is flawed ?
I suspect so, but since I don't know the Canon scanner well (it must be
2 or 3 years since I even saw one!) I can't be sure. How did you get
access to the raw data to confirm that the dark readings were not
changing and that the scanner itself was not calibrating for the
exposure you had defined. Interestingly you found that it did make a
difference at the extreme exposure range could this be where the CCD was
being completely saturated during the calibration?
 
I suspect so, but since I don't know the Canon scanner well (it must be
2 or 3 years since I even saw one!) I can't be sure. How did you get
access to the raw data to confirm that the dark readings were not
changing and that the scanner itself was not calibrating for the
exposure you had defined. Interestingly you found that it did make a
difference at the extreme exposure range could this be where the CCD was
being completely saturated during the calibration?

The testing was done with software I wrote so I know I am not changing
the data. Also, the FS4000 has no memory or capability to change the
readings before sending them to the PC so I am sure it can't do any
calibration.

I don't think CCD saturation is occurring as these are all black level
readings. I do test for saturation during white level testing. The
light/CCD reading relationship drops off after about 40000 (16-bit) when
the analogue gain is 1 so I limit the exposure duty-cycle to avoid this.

I was surprised that my black level readings weren't affected by the
exposure setting especially after I noticed that Vuescan does save the
black readings for all of the speeds that it may use. I haven't
compared the 6 sets of black readings in the VS file but perhaps I
should.

I will do some more testing and save the results.

-- Steven
 
Fernando said:
Markus, see if this helps:

http://gundam.srd.it/PhotoPages/software/dfsub-0.1.zip

It was wrote ot address a Vuescan shortcoming when it comes to
calibrating the 5400, but maybe it could also work with Minolta Scan
Utility, of course if you scan in 16bit Linear mode.
Please have a look at the README.

Thanks, I may try that. However, in my case the line strength is NOT
constant, and I am not sure, if dark frame would produce similar lines.

--markus
 
Markus said:
[snip]
I don't have a Minolta scanner so I can't try this, but in another thread
Bart mentioned that you can force a calibration by using Ctrl-Shift-I, to
re-initialise the scanner. It may be possible, you will have to check, to
lock the exposure to that required for your dark scans by auto-exposing on
them first and then switching off the autoexposure function.
Re-initialising the scanner *may* then perform a calibration with the same
exposure as you are using for the scan and thus create a more accurate
dark current calibration reference.

I will have to try that. It is also interesting, that I have a few 4x
multisampled long scans which are VERY clean indeed. But not all of them...
It just may be possible, that I would have manually calibrated the device
for some reason. It is also true, that the unit often does many automatic
calibrations during first few scans after switching the unit on. After that
it never automatically calibrates.

I guess the grain diffuser complicates dark current issue, since it greatly
reduces light accumulation per time unit?

My default settings on the 5400 is 16 bit max resolution at 4X and
ICE+GD enabled, and the scan time is very long. Yet I have never
encountered the problem you described. I use the Minolta sw.

I assume that the 5400 calibrates after powering up, but after that I
can't tell if it calibrates automatically. There are lots of squeaking
after applying AF or MF in prescan, or after adjusting the Exposure
Control tab, or clicking the Prescan button. The noise can be attributed
to moving the focusing mechanism, but it can also imply other
calibrations.
With Minolta software it is possible to adjust exposure based on a
"standard" exposure, you just turn off the autoexposure. With prescan it is
easy to adjust exposure so that the result is dark, but hopefully has enough
information.

There is quite a range of exposure controls on the 5400 including an
Exposure Lock button and the ability to save and load an exposure
setting file. It isn't clear whether these controls are for the hw or sw
exposure settings. I use the hw Exposure Control tab only, and adjust
the sliders until the histograms are free of clippings. The Exposure
Lock and file both work fine for these settings.

Be careful with the Auto Exposure option in the Preference. It must be
enabled for slides and to use the Exposure Lock button. Kind of screwy.
 
If you use the same exposure for the dark scan ,and of course if you
work in 16 bits/channel Linear, the dark scan should have ... "similar"
lines. :)

Let me know if you end up with something useful. :)

Fernando
 
Be careful with the Auto Exposure option in the Preference. It must be
enabled for slides and to use the Exposure Lock button. Kind of
screwy.

Ah!!!! This solves an ancient doubt of mine!! Thanks!! :D

Fernando
 
Fernando said:
screwy.

Ah!!!! This solves an ancient doubt of mine!! Thanks!! :D

Fernando

You are welcome. It's in the manual, which apparently was written by
someone whose native tongue is not English. There was a time (50s to
70s) when "English" manuals of Japanese products were hardly
decipherable and great examples of language mutilation.
 
I was surprised that my black level readings weren't affected by the
exposure setting especially after I noticed that Vuescan does save the
black readings for all of the speeds that it may use. I haven't
compared the 6 sets of black readings in the VS file but perhaps I
should.

I will do some more testing and save the results.

Following up my own post.

Here are the averages from a VS calibration file

R G B
Average = 59725 52883 54619 white lamp on
Average = 11103 4310 3373 IR lamp on
Average = 647 1130 1253 lamp off, exposure 2
Average = 652 1130 1252 lamp off, exposure 4
Average = 662 1134 1255 lamp off, exposure 6
Average = 672 1138 1257 lamp off, exposure 8
Average = 683 1141 1259 lamp off, exposure 10
Average = 692 1144 1262 lamp off, exposure 12

So, yes, the levels do increase at longer exposures but not much.

If I do a similar test I get comparable results. However, normally I
set the analogue offsets to get lower values. With the extra offset the
values don't change across the exposure range.

The FS4000 precedes each 4000 pixel scan line with a 40 pixel black
margin. I'm not sure why this is done but it does change across the
exposure range even though the scan line values don't.

/--- scan line ---------\ /------ margin ---------\
Exp 1, R 58, G 107, B 118, R 42, G 84, B 97
Exp 2, R 58, G 107, B 118, R 46, G 92, B 108
Exp 3, R 57, G 105, B 117, R 53, G 100, B 115
Exp 4, R 56, G 104, B 115, R 55, G 109, B 126
Exp 5, R 56, G 102, B 114, R 60, G 117, B 131
Exp 6, R 54, G 101, B 112, R 70, G 130, B 139
Exp 8, R 52, G 97, B 107, R 80, G 150, B 158
Exp 10, R 57, G 101, B 112, R 94, G 170, B 175
Exp 12, R 61, G 108, B 117, R 111, G 185, B 192

I don't know the purpose of this margin that precedes each line but it
looks like a base noise level for the line and might be used to adjust
the following pixels before the data is output to the PC. Does this
sound reasonable ? This may explain why I am not seeing an increase of
black levels at long exposures.

-- Steven
 
Steven said:
Following up my own post.

Here are the averages from a VS calibration file

R G B
Average = 59725 52883 54619 white lamp on
Average = 11103 4310 3373 IR lamp on
Average = 647 1130 1253 lamp off, exposure 2
Average = 652 1130 1252 lamp off, exposure 4
Average = 662 1134 1255 lamp off, exposure 6
Average = 672 1138 1257 lamp off, exposure 8
Average = 683 1141 1259 lamp off, exposure 10
Average = 692 1144 1262 lamp off, exposure 12

So, yes, the levels do increase at longer exposures but not much.
It might not seem much, but if you consider that this is linear data and
the error from the black level after calibration will then be scaled by
the gamma compensation, it is very significant.

For example, just looking at green (red would be a lot worse whilst blue
a little better) if the exposure 2 figure was used, but the exposure was
actually 12 (which is not unexpected for a long exposure) then the
residual average black would be 14 too high. Consequently, when
compensated for gamma 2.2, this would produce a result that was 1406 on
the 16 bit range, or 5 on Photoshop's 0-255 levels range - which are
very visible offsets from black. This is a perennial problem with CCDs
which require dark current correction in linear and are only converted
to gamma compensated output later - those small errors are very
significant.

However, it isn't the average RGB levels in each exposure range that
matters, but the maximum change. Those are the pixels that have a high
dark current level and consequently will change most with exposure. Note
that dark current isn't the only thing that gives rise to a dark field
signal - there are threshold variations across the chip as well as
general offsets between the output and the ADC reference datum. You
would probably consider a change in red from 0 to 45 to be significant.
But it is no worse than you are getting for the average, and I bet that
a few lines are significantly worse than that - these are the lines that
will be most visible in the scan.
If I do a similar test I get comparable results. However, normally I
set the analogue offsets to get lower values. With the extra offset the
values don't change across the exposure range.

The FS4000 precedes each 4000 pixel scan line with a 40 pixel black
margin. I'm not sure why this is done but it does change across the
exposure range even though the scan line values don't.

/--- scan line ---------\ /------ margin ---------\
Exp 1, R 58, G 107, B 118, R 42, G 84, B 97
Exp 2, R 58, G 107, B 118, R 46, G 92, B 108
Exp 3, R 57, G 105, B 117, R 53, G 100, B 115
Exp 4, R 56, G 104, B 115, R 55, G 109, B 126
Exp 5, R 56, G 102, B 114, R 60, G 117, B 131
Exp 6, R 54, G 101, B 112, R 70, G 130, B 139
Exp 8, R 52, G 97, B 107, R 80, G 150, B 158
Exp 10, R 57, G 101, B 112, R 94, G 170, B 175
Exp 12, R 61, G 108, B 117, R 111, G 185, B 192

I don't know the purpose of this margin that precedes each line but it
looks like a base noise level for the line and might be used to adjust
the following pixels before the data is output to the PC. Does this
sound reasonable ? This may explain why I am not seeing an increase of
black levels at long exposures.
It appears, from the above data, that the increase in dark signal to the
longer exposure is being compensated by the margin. Many CCDs have
guard pixels on either side specifically for this purpose and the
average of those guard pixels is subtracted from the signal pixels
either on the CCD output itself or off-chip. However it has no effect
on the dark current distribution, or non-unformity, and it is the
non-uniformy and its change that is significant here.

It might help in understanding this if you draw a distinction between
noise and signal. The dark current is just a signal, albeit an unwanted
one. Variation of that dark current, both across the CCD from pixel to
pixel, and with time, ie. from sample to sample of the same pixel, is
noise. So the margin cannot be a base noise level, but it can be an
average base signal.
 
There was a time (50s to
70s) when "English" manuals of Japanese products were hardly
decipherable and great examples of language mutilation.

And looking back they were quite amusing! Although it did not appear
so at the time... ;o)

Still happens occasionally but is not as common.

Don.
 
Back
Top