Page History

Status on follow-ups

Data from HSI

Hardware

Software

IdleTech

Communications

Mission Design

for last weeks action items

•  Not complete (week 40) Mariusz Eivind Grøtte Get preliminary results from EOIR tool in STK (or MODTRAN) on "what can we see from space"

•  Not complete (week 40) Unknown User (julianve) First revision of PCB

•  Complete Unknown User (julianve) Start with purchasing parts (like devboard etc.) for h/w
•  Not complete (week 40) Unknown User (rogerbi) A cost benefit analysis of power usage vs compression for comms.
•  Not complete (week 40) Unknown User (rogerbi) 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. 
•  Complete Mariusz Eivind Grøtte CAD model of HSI lenses
•  Not complete (week 40) Unknown User (sivertba) Find a student to do thermal analysis and coordinate with Mariusz

• • Mariusz: On the look still, but the PhD student at Materials Sciences has shown great interest. Also the PhD student's professor is interested. Need to set requirements on beforehand before discussions and testing may start.
  • A requirements document is being worked on. Shall start discussions next week.

•  Complete Unknown User (orlandic) Continue work on software architecture and coordinate with Idletechs

• • This is still to be coordinated this week. Need more follow ups for Idletechs

•  Not complete (week 40) Unknown User (joaoff) Report of what has been done with HSI imaging
•  Not complete (week 40) Give feedback on Gantt chart (ALL) - Still want a list of activities from each - respond to emails

Data from HSI

• Joao is writing a report on what has been done on HSI imaging with drones.
  • Working on what has been done in three drone campaigns. Underway with report. 
• Developing a statistically sound method for determining signal/noise levels.

Hardware

• Julian has ordered HW parts (devboard etc.)
• Mariusz has designed the CAD for HSI lenses (more action items on it below)
  • Focal lengths should be ok but unsure about apertures
  • Julian needs to see how it fits on PCB
• First PCB still in revision
• Please put in more here Julian

General Discussions

HSI Camera discussion

• Going through Fred’s calculations for version 4. Some dimensions specified do not make sense when modelled (reverse engineering).
• Slit width too small? Apertures are not correct.
• Bits/pixel
• Binning

SNR

• Treating it differently than usual definition
• Generalizing such that we take out what we want to see, but treat unwanted spectral responses as noise
• Read-out noise, background noise, dark current noise
• RMS values assumed (not peak values)

Software

• Software architecture
• Talks about stages of processing
• Please put in here Milica

Need to follow up on (request for Idletechs):

• What processors are onboard, how do they connect, what capacity do they have (memory, processing architecture, clock frequency etc.)
• What processes run on which processors, how do these processors communicate and synchronize and are monitored.
  • Message based interprocess communications? Shared memory?
  • Data formats
• What operative system and which compilators are used, as well as other third party components.

IdleTechs

• A memo for data compression has been started on, 
  • listing some requirements for compression
  • outlining a solution
  • commenting on how well the suggested solution fits to the requirements.  
• A copy can be found in the project wiki.
• A preliminary estimate indicates that the data from one patch can be compressed to be downloadable in less than one minute through a 1 Mbit/s link (S-band).

Communications

• None

Mission Design

• Has investigated on technicalities for slewing maneuver such as:
  • Pitch-Roll-Yaw sequence (what order is optimal in terms of time and energy)
  • Investigated slewing functionality in STK
    • Set 1 deg/s and 0.1 deg/s^2 constraints
    • Max slew time = 30 sec
    • Adaptive step size control
    • Start slew at line of sight
    • GSD = 100 m
  • Need to figure out power consumption
  • Limitations on ground precision in simulations.
• Analysis of time-window for observation (morning), 3 access times (4^th is not viable - too high small elevation angle)
  • First pass: 1 min
  • Second pass: 3 min
  • Third pass: 55 seconds
• Lost access to license for EOIR-add on in STK but
  • Done some reading on how it works
  • integrate with MODTRAN (separate software costs 4000 USD)
  • may get spectral response with own-defined resolution (transmission and reflectance)
  • may model BRDF properties of ocean
  • photon flux/photon detectors
  • assumes unpolarized sensor
  • saturation may be enabled
  • Figures out SNR due to sensor dark noise and scene photon noise (background radiance/electrons)
  • Expect graphs/simulations/results next week!

Actions ahead

• Mariusz: Request requirements for the RCN technical report due 10^th Nov (and review presentation 6^th of December) from Tor Arne
• Mariusz and Julian: Get information on the dimensions of Fred’s lenses for CAD drawings
  • Lenses aperture
  • Lenses focal length
  • Slit width and height (seems extremely small??)
  • Get a person/student to do the mechanical drawings
• Mariusz and Julian: Find a student for thermal testing (both physical hardware and thermal simulations for CAD)
• Mariusz and Julian: Draw a prototype CAD for encasing around lenses (the CAD we have now is difficult)
• Roger: access to wiki for Jan Otto and Julian
• Mariusz: Simulate slew maneuver with specified push-broom scanning and GSD<100 m
• Milica: Find student to do JPEG2000 compression
• Milica: 
  • What processors are onboard, how do they connect, what capacity do they have (memory, processing architecture, clock frequency etc.)
  • What processes run on which processors, how do these processors communicate and synchronize and are monitored.
    • Message based interprocess communications? Shared memory?
    • Data formats
  • What operative system and which compilators are used, as well as other third party components.
• All: update Gantt chart