<?xml version="1.0" encoding="utf-8"?>
<rss version="2.0" 
    xmlns:dc="http://purl.org/dc/elements/1.1/"
    xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
    xmlns:admin="http://webns.net/mvcb/"
    xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#"
    xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:itunes="http://www.itunes.com/dtds/podcast-1.0.dtd">
	<channel>
<title>Custom Visuals Feed</title><link>http://www.customvisuals.com/index.html</link><description>Custom Visuals News</description><dc:language>en</dc:language><dc:creator>mgs@customvisuals.com</dc:creator><dc:rights>Copyright 2009-2011 Custom Visuals&#x2c; LLC</dc:rights><dc:date>2009-08-23T11:51:43-05:00</dc:date><admin:generatorAgent rdf:resource="http://www.realmacsoftware.com/" />
<admin:errorReportsTo rdf:resource="mailto:mgs@customvisuals.com" /><sy:updatePeriod>hourly</sy:updatePeriod>
<sy:updateFrequency>1</sy:updateFrequency>
<sy:updateBase>2000-01-01T12:00+00:00</sy:updateBase>
<lastBuildDate>Fri, 26 Jun 2009 21:47:05 -0500</lastBuildDate><item><title>Hughes Budget Cutoff</title><dc:creator>mgs@customvisuals.com</dc:creator><category>Satellite</category><category>Defense</category><category>IDL</category><dc:date>2009-08-23T11:51:43-05:00</dc:date><link>http://www.customvisuals.com/weblog/files/39937a6ed7bb9325b99c61d9fa283959-3.php#unique-entry-id-3</link><guid isPermaLink="true">http://www.customvisuals.com/weblog/files/39937a6ed7bb9325b99c61d9fa283959-3.php#unique-entry-id-3</guid><content:encoded><![CDATA[Back in 1995, I was working for Hughes Aircraft Company, Santa Barbara Research Center (SBRC) on a project called Wedge Imaging Spectrometer (WIS).   WIS was a hyper-spectral sensor capable of up to 722 bands of data from UV through Thermal IR, depending on the instruments used for each mission. ...  One way to think of it is that any pixel on a typical computer screen is generated from 24 bits of color, WIS generated over 8,000 bits of color per pixel.


While working on this project, we had budgets within Hughes for projects, hardware, software, etc., each budget essentially a different bucket that could not be mixed together.   Early into the year, our software budget was cut just as we had a purchase requisition in the pipeline for Research Systems&rsquo; <a href=&rdquo;http://www.ittvis.com/ProductServices/ENVI.aspx&rdquo;>ENVI</a> (now part of ITT).   This is a high end image processing and remote sensing package that is aimed straight at the type of data WIS produced, so it was a natural match to help develop and analyze WIS products.   The purchase requisition was for somewhere in the $8,000 range if I recall correctly, but we were unable to purchase it due to the budget cut. ...  The following year, we put ENVI in as the first item to purchase for our project and received it immediately. ...  Considering my salary, overhead costs, lost time to work on other tools, etc., Hughes un-saved about $90,000 by eliminating the $8,000 purchase order.


...During the year this budget issue took place, I switched from an employee to a consultant/contractor for Hughes and also began teaching IDL classes (ENVI is written in IDL) outside of Hughes for Research Systems.   One of the items I negotiated with Research Systems as part of teaching the training classes was an ENVI license for my own use. ...  By the time WIS was utilizing ENVI to a larger degree for processing and analysis, I was pretty much the only person familiar with the software on the team and I was working less on the project.   About a year later, I left the SBRC division and started working completely on my own not too much longer after that.
]]></content:encoded></item><item><title>NASA Program Language Requirements</title><dc:creator>mgs@customvisuals.com</dc:creator><category>Satellite</category><category>Defense</category><category>IDL</category><category>PV-Wave</category><dc:date>2009-07-11T06:01:18-05:00</dc:date><link>http://www.customvisuals.com/weblog/files/33d39e71809d80a10a6fd298e949d03b-2.php#unique-entry-id-2</link><guid isPermaLink="true">http://www.customvisuals.com/weblog/files/33d39e71809d80a10a6fd298e949d03b-2.php#unique-entry-id-2</guid><content:encoded><![CDATA[The <a href=&rdquo;http://modis.gsfc.nasa.gov/&ldquo;>MODIS</a> satellite sensor was being built by Hughes and I was tasked with building an algorithm test bed for it.   The group I was part of had spent several years working with the <a href=&rdquo;http://www.ittvis.com/ProductServices/IDL.aspx&rdquo;>IDL</a> programming language and had sent me off to an IDL class at Research Systems&rsquo; (the IDL developers, now a division of ITT) offices in Colorado. 

...As specified in the program specs, we had to deliver all new code in either C or PV-Wave, IDL would not be accepted.   We pushed back for some clarification on that, and it was reiterated that IDL could not be used because PV-Wave was specified by NASA.   This wasn&rsquo;t a huge issue since PV-Wave was based on a copy of the IDL source code sold from Research Systems to Visual Numerics. ...  In the years after the source code had been sold, both companies had developed it in parallel, but different ways. 

...As it happens, a large portion of what I was working on required a GUI for the engineers to be able to quickly load, apply and view the results of varying algorithms, so this had a pretty big effect on me. ...  Also, functions that had some options in IDL had different options in PV-Wave as both companies extended the language in different ways. 

...After about 3 months of development, we were demoing our applications for NASA on their systems when we hit a snag.   After loading our code and data and bringing up the GUI to start processing some of the data, a dialog box came up indicating we were not licensed to load the data.   After bringing in a couple of the technical staff, it was determined that the NASA team we were working with had not purchased PV-Wave for the project, they had just requested a demo license and had never run it beyond watching the demo screens. ...  It cost some additional time in development for me to come up to speed with the PV-Wave way of GUI design and the occasional issue of having to rewrite functions from our IDL library to work within the PV-Wave library.


The project continued on in PV-Wave of course, and was eventually completed, delivered and accepted along with all of the other software, hardware, manuals, etc. that you might imagine goes along with providing a sensor that will spend years operating in a satellite.  ]]></content:encoded></item><item><title>WxGRIB I</title><dc:creator>mgs@customvisuals.com</dc:creator><category>Weather</category><dc:date>2009-07-03T05:53:31-05:00</dc:date><link>http://www.customvisuals.com/weblog/files/aaff3c06369aaa579d887d8a9c9f5fd6-1.php#unique-entry-id-1</link><guid isPermaLink="true">http://www.customvisuals.com/weblog/files/aaff3c06369aaa579d887d8a9c9f5fd6-1.php#unique-entry-id-1</guid><content:encoded><![CDATA[Quite a while ago I started a project where we needed to do some data processing to pull out a couple parameters from NOAA GRIB data.   The project had a very limited scope, and was completed sometime in the middle of 2008.   I&rsquo;ve also been playing with Google Maps and Google Earth API&rsquo;s over the last couple of years and am planning to integrate the GRIB data and Google API&rsquo;s to see what kind of forecasting information can be generated from the data and how it can be presented.


I&rsquo;m rebuilding the entire processing stream from the ground up since the limited scope mentioned previously does not extend itself to processing of the entire dataset in an efficient manner.   Starting with the initial download of the index files from the website, to conversion of the full files to a format useful for a database is only mildly complicated.   What makes it a bit more entertaining is to do this as quickly and efficiently as computer resources can manage.


I built a quick prototype of this recently to see what kinds of problems I would run into before getting to the optimization stage.   Trying to throttle things with semaphore files and system load checks caused the system to run under an excessive load (uptime load > 20), and for some of the lower priority stages to get ahead of the higher priority stages.   So, the 2nd prototype is now under development.   This time around I&rsquo;m using Parallel::ForkManager for the first time.   That should make it easier to control the stages and keep things running in a more orderly fashion.


Hopefully, there will be a much smaller &ldquo;lessons learned&rdquo; phase after this.]]></content:encoded></item><item><title>New Site Design. Finally&#x21;</title><dc:creator>mgs@customvisuals.com</dc:creator><category>General</category><dc:date>2009-06-26T21:47:30-05:00</dc:date><link>http://www.customvisuals.com/weblog/files/7299827b1161e1bcfcb09d1f017a988c-0.php#unique-entry-id-0</link><guid isPermaLink="true">http://www.customvisuals.com/weblog/files/7299827b1161e1bcfcb09d1f017a988c-0.php#unique-entry-id-0</guid><content:encoded><![CDATA[A new site design was long overdue and has finally made it out of the gate.   We&rsquo;ve created a few over the last couple years and abandoned them before ever taking them live.   Either the design just wasn&rsquo;t what we wanted to present, or the technology we wanted to use just made things more painful to update than practical.   We finally went with <a href="http://www.realmacsoftware.com/rapidweaver/">Real Mac Software&rsquo;s RapidWeaver</a>, which seems like the right blend of ease of use, functionality, customization and expandability.]]></content:encoded></item></channel>
</rss>
