Unfortunately the Bayer CFA is a collection of colored filters bonded to each pixel on the chip. The only way to remove it would be to replace the whole sensor chip with a replacement monochrome chip.
There have been some mono digital cameras in the past (e.g. the DCS 760M) but unfortunately they've all had their flaws and there are none currently on the market.
While I would love a good mono camera I'm not sure any camera manufacturer has been convinced that there's enough of a market out there to introduce one...
My first reaction was along the lines of "Man, that's asking for trouble". It'd be a fun toy to make, but once you fire a few disks you'll get an understanding of how dangerous this is. I know I'm not the only one to comment on this, but what the hey...
My experience is only with hand-thrown CDs (at a distance of 15m or so) but:
If one hits you and it "only hurts" you were probably lucky.
CDs can easily embed themselves in plasterboard walls.
They shatter easily on impact, and yes those shards are SHARP.
They're REALLY hard to aim. They're not as stable as a frisbee, and can wobble and twist in mid-air. It's not a nice feeling when you see one drifting off-target and towards an innocent target (e.g. a child or your boss's boss).
Sure, you can have fun designing a machine, but it's a downright dangerous result you're looking for. Can't you exercise your brain with a safer problem?
The DEC ones were surprisingly nice to use (especially compared to some of the other choices of the time). No, I wouldn't choose one now, but that was then and this is now.
One of their features was lack of a ball. They had two tilted wheels underneath which picked up movement on each axis. Because of this they rarely clagged up with desk fluff, and as a result were quite reliable. I think Honeywell later released a (non-round) mouse with a similar mechanism for PCs.
... some oddities... like one with a crosshair attachment for clicking on specific points of a blueprint for CAD input.
Strictly speaking these were "pucks" for tablets (which weren't restricted to relative positioning) rather than "mice" (although I'm not sure how official that distinction is).
Some (high-end) cameras will record GPS data inside the EXIF block of an image, but they typically need a GPS unit attached via a serial cable. This has been around for years.
I do this a different way: when on trips where I have a GPS running, I download the track data at the end of the day. The clocks in my cameras are close enough to "real" time that it's easy to correlate the time on the photos with the times in the GPS data.
I guess having a camera that transfers its images to a PC automatically would sound like a "neat thing" to many product designers. Not being intimate with Bluetooth I don't know if this is an issue, but I immediately thought about someone wandering around town with a Bluetooth-equipped machine in a backpack silently downloading images from all the tourists milling around...
HTTPS through a proxy simply uses the CONNECT method to get a direct connection to the SSL server at the other end. It requires an end-to-end byte stream.
The proxy can sniff the traffic, but they then need to decode the SSL...
I would have expected to see a question like this directed to one of the sysadmin guilds you're probably a member of (what, you're not?). If you were a member of SAGE, you would be aware of the SAGE Code of Ethics. SAGE-AU has an equivalent code.
In the SAGE code it mentions:
System administrators will not exercise their special powers to access any private information other than when necessary to their role as system managers, and then only to the degree necessary to perform that role, while remaining within established site policies.
So, the bottom line: What do your organisation's policies allow?
The usual path for this sort of stuff is to get the managers in question to publish a policy (even if it's something as crappy as voicemail to all employees warning them of the policy and the consequences of breaching it). It often helps to provide a draft policy to get them started down a reasonable path. Then your tasks are clearly defined. Without a published policy you and your managers are walking in a minefield.
Keep in mind that the published codes are there to protect you as much as anyone else. If a manager tries to force you to act against your principles you have a recourse. As a member of a guild you can point to the published code of ethics and say "sorry, I cannot do that". "And neither will any other ethical sysadmin".
Whatever you do, get your instructions from management in writing.
Certainly most Linux stuff is Open Source, but not all Open Source is Linux. I would go so far as to guess that it's in the minority. Am I wrong in thinking that Linux is the kernel, and Open Source application software typically runs on platforms that includes Linux? For example, I write lots of open source code, but I have no interest in using Tux (disregarding his licence retrictions for the moment).
Yes I admit bias - my notebook runs FreeBSD:) I don't want to start a religious discussion, but I had trouble letting your assumption go unchallenged...
Slashdot Mirror
Unfortunately the Bayer CFA is a collection of colored filters bonded to each pixel on the chip. The only way to remove it would be to replace the whole sensor chip with a replacement monochrome chip.
There have been some mono digital cameras in the past (e.g. the DCS 760M) but unfortunately they've all had their flaws and there are none currently on the market.
While I would love a good mono camera I'm not sure any camera manufacturer has been convinced that there's enough of a market out there to introduce one...
My first reaction was along the lines of "Man, that's asking for trouble". It'd be a fun toy to make, but once you fire a few disks you'll get an understanding of how dangerous this is. I know I'm not the only one to comment on this, but what the hey...
My experience is only with hand-thrown CDs (at a distance of 15m or so) but:
Sure, you can have fun designing a machine, but it's a downright dangerous result you're looking for. Can't you exercise your brain with a safer problem?
Like nuclear fission... ;-)
The DEC ones were surprisingly nice to use (especially compared to some of the other choices of the time). No, I wouldn't choose one now, but that was then and this is now.
One of their features was lack of a ball. They had two tilted wheels underneath which picked up movement on each axis. Because of this they rarely clagged up with desk fluff, and as a result were quite reliable.
I think Honeywell later released a (non-round) mouse with a similar mechanism for PCs.
... some oddities ... like one with a crosshair attachment for clicking on specific points of a blueprint for CAD input.
Strictly speaking these were "pucks" for tablets (which weren't restricted to relative positioning) rather than "mice" (although I'm not sure how official that distinction is).
Not just "does it appear as a USB Mass Storage device with a convenient filesystem format", but also:
Is the recorded audio (e.g. voice recordings) in a format easily accessible using Open Source tools?
If the answer to both of those was yes then I'd probably buy one without hestitation. Does anyone have one they're willing to post a review of?
Some (high-end) cameras will record GPS data inside the EXIF block of an image, but they typically need a GPS unit attached via a serial cable. This has been around for years.
I do this a different way: when on trips where I have a GPS running, I download the track data at the end of the day. The clocks in my cameras are close enough to "real" time that it's easy to correlate the time on the photos with the times in the GPS data.
I guess having a camera that transfers its images to a PC automatically would sound like a "neat thing" to many product designers. Not being intimate with Bluetooth I don't know if this is an issue, but I immediately thought about someone wandering around town with a Bluetooth-equipped machine in a backpack silently downloading images from all the tourists milling around...
HTTPS through a proxy simply uses the CONNECT method to get a direct connection to the SSL server at the other end. It requires an end-to-end byte stream.
The proxy can sniff the traffic, but they then need to decode the SSL...
If you read the C|Net page carefully you will see it says the machines are to be 4-CPU Compaq boxes running Tru64 Unix.
The writer did mention Beowulf, but only to say that it was similar.
__
Conclusions are easy to jump to. Just be prepared to jump again...
I would have expected to see a question like this directed to one of the sysadmin guilds you're probably a member of (what, you're not?). If you were a member of SAGE, you would be aware of the SAGE Code of Ethics. SAGE-AU has an equivalent code.
In the SAGE code it mentions:
So, the bottom line: What do your organisation's policies allow?The usual path for this sort of stuff is to get the managers in question to publish a policy (even if it's something as crappy as voicemail to all employees warning them of the policy and the consequences of breaching it). It often helps to provide a draft policy to get them started down a reasonable path.
Then your tasks are clearly defined. Without a published policy you and your managers are walking in a minefield.
Keep in mind that the published codes are there to protect you as much as anyone else. If a manager tries to force you to act against your principles you have a recourse. As a member of a guild you can point to the published code of ethics and say "sorry, I cannot do that". "And neither will any other ethical sysadmin".
Whatever you do, get your instructions from management in writing.
Sigh...
:)
Certainly most Linux stuff is Open Source, but not all Open Source is Linux. I would go so far as to guess that it's in the minority. Am I wrong in thinking that Linux is the kernel, and Open Source application software typically runs on platforms that includes Linux? For example, I write lots of open source code, but I have no interest in using Tux (disregarding his licence retrictions for the moment).
Yes I admit bias - my notebook runs FreeBSD
I don't want to start a religious discussion, but I had trouble letting your assumption go unchallenged...