|
It was some sort of very high end generic image processing tool not a specific tool for astronomers; and since I'm blanking on the name I obviously can't answer the second question.
Did you ever see history portrayed as an old man with a wise brow and pulseless heart, waging all things in the balance of reason?
Is not rather the genius of history like an eternal, imploring maiden, full of fire, with a burning heart and flaming soul, humanly warm and humanly beautiful?
--Zachris Topelius
Training a telescope on one’s own belly button will only reveal lint. You like that? You go right on staring at it. I prefer looking at galaxies.
-- Sarah Hoyt
|
|
|
|
|
|
After Googling for a few lists of software I think it might be Mira[^]; the headline feature set (focused on data analysis not making pretty pictures for the web) is right for the market segment and the name sounds vaguely familiar. The price for their top end variant Mira MX is around $3k depending on if you qualify for the academic discount or not and personal vs single user licenses (not immediately obvious what the difference is).
Did you ever see history portrayed as an old man with a wise brow and pulseless heart, waging all things in the balance of reason?
Is not rather the genius of history like an eternal, imploring maiden, full of fire, with a burning heart and flaming soul, humanly warm and humanly beautiful?
--Zachris Topelius
Training a telescope on one’s own belly button will only reveal lint. You like that? You go right on staring at it. I prefer looking at galaxies.
-- Sarah Hoyt
|
|
|
|
|
Wow! Seems to be a great tool for scientists and engineers. What is interesting is a quote from their homepage:
In 1994, Mira users were working with 250MB survey images (and doing smooth, real time display adjustments too) using 486 class PC's. Must have done real programming gymnastics to achieve that!
A few years ago, I had the opportunity to work with iSee[^], which is an image analysis tool, for Non-Destructive Inspection, with a much lesser feature set.
|
|
|
|
|
Yeah, I'm assuming image chunking and streaming from the HDD probably was a big part of it. 1024x768 probably helped a lot too, but even then you probably couldn't hold more than one or two screens worth of scroll in ram (16mb max??) at a time.
Did you ever see history portrayed as an old man with a wise brow and pulseless heart, waging all things in the balance of reason?
Is not rather the genius of history like an eternal, imploring maiden, full of fire, with a burning heart and flaming soul, humanly warm and humanly beautiful?
--Zachris Topelius
Training a telescope on one’s own belly button will only reveal lint. You like that? You go right on staring at it. I prefer looking at galaxies.
-- Sarah Hoyt
|
|
|
|
|
|
We were regularly doing image warping in the early 80s, pasting multiple satellite images together. The data is actually continuous in the north-south orbital path, but the side-by side has to be joined and then converted to a mapping projection scheme.
I worked at JPL in 1983 after using their software as a state tech-transfer cooperator since 1973. The image processing software ran on an IBM 350 mainframe and in about '84 the software production moved to a DEC VAX cluster. but that's beside the point; the software was called "Video Image Communication And Retrieval", or VICAR.
http://www-mipl.jpl.nasa.gov/external/vicar.html
"Video" because it came out of the first moon orbital pictures (Ranger) and they literally were done in video. In the earliest days we printed on strips of paper and colored different letters with felt pens, then hung the strips on the wall and taped them together to try and visualize what the data contained. I did meet the fellow who did the original pictures of Jupiter, both before the first fly-by and after from real data. His computer was an ancient (by that time) PDP 8 (If I recall correctly) with only a paper-tape for I/O.
Fond memory of Buzz Slye at Moffett Field who drove a TR3 and still kept his code on card decks in the early 90s. Buzz wrote a series of statistical multi-spectral classifiers as part of the research into computer recognition of agricultural crop types. If he were still with us, his cards would still be readable. I tossed my 9-track 6250 tapes about a decade ago.
|
|
|
|
|
Really honored to get a reply from someone so well-versed and experienced as you. Lesser mortals like me don't have such first-hand experiences.
Regarding your Jupiter reference, I believe you're referring to the Voyager 1 and 2 pictures. As a just-joining-college student in 1981, I had seen a film show (at an institution called the Raman Research Institute in Bangalore, India) on Voyager 2's journey with close-up shots of Jupiter. Really fascinating for a student like me. Especially the Giant Red Spot, seen in slow-motion, was mind-blowing. [Had heard that Voyager 2 reached Jupiter earlier than Voyager 1, and that the movie showed pictures taken from Voyager 2].
VICAR seems to be a great software, and they even announce that it is being released as open-source. Looks like that has not yet happened. Am keen to download and study the code - even trying to understand the code would be a great educating and enlightening experience.
One question: Before you discarded your 9-track tapes, did you backup the code on a more modern storage device?
|
|
|
|
|
I was hardly well versed; more like a member of the coding user community and a rather junior one at that!
the code I worked with starting in the early 80s was adapting VICAR IBM batch code to work with an IIS image processing display system. That system was controlled by a PDP-11/34 with all of 256K of memory and three 5mb removable drives! the IIS machine could store in memory 8 512/512/8bit images on 9 printed circuit cards for each image (8k chips). It had hardware lookup tables as well as a pipeline processor for image to image math operations. by the 90s that was an updated IIS machine (64k chips, one board per image, 32 image channels) driven by a VAX.
I left that business in '96 and about 10 years later gave my personal archive tape to my former boss who tried to have the contents read by a contractor; the attempt failed. The code was still on an old MicroVAX, but it went to the landfill around the same time.
working with code written by the early heavy lifters had a huge impact on my coding career. The IBM version of VICAR was a "language" where a series of commands resulted in a string of image processing operations to be executed. The JCL controlled the files, the language processor was in assembler, and the individual modules controlled by the executive were all in FORTRAN. As a young upstart I once made the comment that wouldn't interactive be better, then you could see what you were producing much faster? The answer I got was "If you know what you are doing and what you are doing is worthwhile, then it is worth waiting for it."
Maybe VICAR was "An elegant weapon, for a more civilized age"
for a text from the early days, see Ken Castleman's Digital Image Processing (http://www.amazon.com/Digital-Image-Processing-Kenneth-Castleman/dp/0132114674[^]) - it was pretty cool to be able to take a class from him.
|
|
|
|
|
As someone whose hobby is astrophotography (and, to toot my own horn a bit, has 4 APODs to his credit), I thought I'd chime in here. 
For a bit of background, like the folks at NASA and other professional observatories, I use a monochrome astronomical CCD camera with color filters to take my images. I use a few different software packages for image processing, including Photoshop and others that are specifically designed for astronomical images.
The objects we shoot are extraordinarily faint. Even after hours and hours of exposure time, if you opened a typical image in Photoshop it would appear essentially black. It takes a lot of stretching and massaging to just make the objects visible. As one of my friends put it, we're trying to take a scene shot at night and make it look like it was taken in daylight. All that said, I think it's very safe to say that our goals as astrophotograpers are, at least for RGB/true color shots, to make the images look as real as we can while also displaying as much of the data as possible. This by nature requires a bunch of "selective adjustments" to keep from blowing out highlights when trying to bring out extremely faint stuff -- the dynamic range is huge. We also go through all sorts of steps to balance the color so that it's as accurate as possible. Sure there's artistic license taken -- this is about as much of a blur between art and science as you can get -- but it's definitely not "fake" or a "lie".
Just my 2 cents...
|
|
|
|
|
|
Coffee?
|
|
|
|
|
What else could it be?
The symbols mean: Heaven = fire + water + earth (or take coffee (earth coloured) and water and heat
And you're up tomorrow!
|
|
|
|
|
Awesome. I thought they almost looked like a syringe: the most effective way of injecting coffee into your day 
|
|
|
|
|
|
Good to know. I think I'm going to treat him for a little ride next weekend.
The language is JavaScript. that of Mordor, which I will not utter here
This is Javascript. If you put big wheels and a racing stripe on a golf cart, it's still a f***ing golf cart.
"I don't know, extraterrestrial?"
"You mean like from space?"
"No, from Canada."
If software development were a circus, we would all be the clowns.
|
|
|
|
|
No that's not Bob!
Bob is an abstract entity 
With friendly greetings,
Eric Goedhart
|
|
|
|
|
Just got an e-mail from my Son's Cubs Leader. She has informed me that tomorrow they will be doing their Science Badge and "if we have anything Science at home, please bring it in".
The thing is I'm struggling to think of anything in my house that isn't "Science" in one way or another. I might need to phone Pickfords and get them to send a truck over so I can take everything in my House along, including myself.
|
|
|
|
|
|
That stuff is all applied science. Do you have any pure science to share?
|
|
|
|
|
They want
anything Science,
but you are
Computer Science,
so, you need to exclude yourself.
|
|
|
|
|
Take in a knife and then look at the science behind that. If she complains, cut 'er! 
veni bibi saltavi
|
|
|
|
|
PompeyThree wrote: so I can take everything in my House along, including myself.
I'd heard a number of theories about you, but I didn't know any of them were proven... 
Bad command or file name. Bad, bad command! Sit! Stay! Staaaay...
|
|
|
|
|
Build and take in a portable meth lab, then point her to this.[^]
=========================================================
I'm an optoholic - my glass is always half full of vodka.
=========================================================
|
|
|
|
|
Change your name to "Occam" and give him your razor to take in.
|
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
