Skip to content

Milestones

List view

  • No due date
    0/1 issues closed
  • Pick a file based data format, define and document a structure, code a parser.

    No due date
    0/1 issues closed
  • Use the burst1a spreadsheet to derive a function that, given balloon parameters, will return a burst altitude in meters.

    No due date
    0/1 issues closed
  • All general conversions that must happen.

    No due date
    0/1 issues closed
  • Given a latitude, longitude, and elevation, return the v and w wind speeds.

    No due date
  • Test the available interfaces for speed and ease of use with speed being of primary importance. Two main options are pygrib and pydap. Pygrib reads directly from grib files, uses little space, but has annyoing data access patterns. Pydap requires the data to be converted (to inefficient formats) and loaded into a server. The data however is much more easily accessed. These two options must be tested for speed.

    No due date
  • Setup a storage system. This could either mean that load all the data into a database of some sort or parse through all the files. In the end, we may find that while a database could mean more setup, it’ll be much quicker.

    No due date
  • This should take a latitude and longitude as an input and return the elevation of the closest point in it’s record.

    No due date
  • A simple function that is passed a stream location (think STDIN file for testing) and can return the appropriate data.

    No due date