Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: Task marked complete

Date

Attendees

Goals

  • Status of each domain
  • Project management objectives
  • Follow-ups forgotten?
  • CAD-model
  • bug.no

Discussion items

TimeItemWhoNotes
10 minHSI AnalysisUnknown User (joaoff)
5 minSoftwareUnknown User (orlandic) 
5 minHardwareUnknown User (julianve) 

10

min

IdleTechJan Otto 
5 minMission DesignMariusz Eivind Grøtte 
5 minCommunicationsUnknown User (rogerbi) 
5 minWrap-up and action itemsAll 

Action items

Data from HSI

- looking at the data we have from drones 
- glare from water completely saturates the image and destroys the data 
- some students working on atmospheric correcting, deconvolution, geometric- and ground-calibration 
- hard to use data without geometrical correction, can look at what we have as point spectra, but not as images 
- challenge: getting absolute measurements. The instruments has not been calibrated for anything particular, so it’s hard to interpret the amount of chlorophyl etc. In other words, relative analysis is easy, but absolute analysis is hard.

Hardware

- Still designing the PCB, hoping to have first revision by next week.
- need to know how to purchase parts (like devboard, PicoZed etc.) Update: got instructions on how to solve this from Kanna.
- need to know the width/height of the grating so that we can calculate how many pixels it’s necessary to use. Update: got information on this from Joao during the meeting). 

Software

-  sent out report on software architecture to everyone, please read it
-  working on integration between memory and which core is used. 
-  need to know the amount of data that’s being sampled for each data cube. 
-  got more code from Idletechs today.

IdleTech

- data will be a big data set with redundancy in wavelength, redundancy in space (nearby pixels will have similar spectra)
- exploiting both in compression (redundancy, and relevance = small details that could be invisible to humans) 
- OTFP (exploit relevance), Milicia is working on integrating it
- Reducing number of colours using PCA (number of wavelengths that are similar)
- For the downlink: Giving a score for each pixel, and suggests using off-the-shelf software for this part. JPEG2000 - based on wavelets (based on research from Trondheim in the 90s). It’s close to state of the art. 16-bit bit values (lossless and lossy compression). Can cut away details we can’t see. Good scalability in lossy mode so that we can choose how much detail we want to include. 
- Progressive transmission: lets us see a low resolution image while waiting for a high resolution. Available as simple libraries that can be included in the system. 
- Fulfil requirements that Idletechs is aware of.
- Idletechs is preparing a memo for this, please let them know if there are any other 
- Company is interested in using the same technology for other projects 
- Let’s look outside the group for compression experts who can validate Jan-Otto / Idletechs assumptions/solution. 

- should also investigate dark currents, #pixels destroyed etc.

 

Questions from Kanna:
- Will there be metrics to understand loss in the image?
RMS value, dB value - how much is lost in the processing line during compression. 
- suggest using evaluation by humans instead of computer metrics. RMS can deliver a bad result even though the image looks good. 
- Can Idletechs deliver data for optic expert in California? 
- too early, but will be able to do it once we get better data with geometric correction

Communications

-  Roger is on vacation so Mariusz is giving the update from Roger:
-  Basing it on S-band system (1-3 Mbit/s) HSI data (spectral and specially) for 500 sec 
-  Looking at other base stations around the world to be able to downlink even more data
-  Bus update after meeting with all the providers 
-  Will know in October if we can get money to update the base station here to S-band. 
Input from JO: 
processing data takes less power then transmitting data. If we are focusing on power optimisation we should do even more with compression.
- A cost benefit analysis of power usage vs compression might be useful.
Input from Kanna: 
Design of the ground station: Look at the entire stack from the spacecraft, through the air, to the ground station and image storage/handling.
What we need is someone who can work with Roger who can piece the bits together and run the decompression and make sure that the product is correct. And need a data system for storing and archiving. 

Mission Design

- EOIR: Can’t model the atmospheric correction,
- Been doing literature review
- Slewing motion: Looking how the STK SOLIS can optimise the slewing motion. Simulation precision show 10m error (which is good!)
- looking at altitude control during slewing motion 
-Will start iterating on the mission requirements, want to be finalized before NASA meeting in October 
challenges: emails are not being followed up on, so waiting for response from agi.com.
Thermal analysis: Know a PhD candidate that offered with his expertise to guide and instruct on using test facilities for thermal analysis (esp. regarding camera lenses). Find a student, and the rest will be done. 

Follow-up from last meeting

- we got computers to the lab, still don’t know if we have access to the lab.
- we have a gantt chart now that we are working on getting set up for the project.
Input from Joao: He’s been tasked with analysing drone data, but that doesn’t validate anything for space. Can’t say if the imager can be used in space.
- Harald thinks we can get a lot of conclusions from the lagoon data. For space: Glare in the data is an issue. Cross polarisation filter is normally used to remove glare in hyper spectral. 
- Follow up for next week: does glare contain any useful information? If not lets use a cross polarisation filter. Have been seeing three different projects with glare problems. 
Suggestions from Kanna:
1) Look at the literature 
2) Contact the author 
3) Report of what has been done with HSI imaging 
- Kanna has a contact he can ask. Space station has a HSI project we can look at results from. 
Input from Kanna:
- We are not changing the optics. We are using what Fred has made. Don’t bug Fred.
Input from Harald:
- Who will take control of the optics / image, Fred is not interested in doing HSI. 
Answer from Kanna:
- Let’s focus on the drone, don’t worry about 4000ft worry about 400ft.
- Wants a report that describes everything that has been done with the drone for the last two years.

Actions ahead

  • Investigate on whether glare contains any useful information?
    1) Look at the literature
    2) Contact the author 
    3) Report of what has been done with HSI imaging 
  • Get preliminary results from EOIR tool in STK (or MODTRAN) on "what can we see from space"
  • First revision of PCB
  • Start with purchasing parts (like devboard etc.) for h/w
  • A cost benefit analysis of power usage vs compression for comms.
  • Present architecture for ground station, how will it work. Decide when upgrade happens, does that involve getting the total package such as h/w and s/w? And need a data system for storing and archiving.