Presentation is loading. Please wait.

Presentation is loading. Please wait.

Campaign Types used in Rosetta Case Studies Steve Chien Jet Propulsion Laboratory, California Institute of Technology © 2013 California.

Similar presentations


Presentation on theme: "Campaign Types used in Rosetta Case Studies Steve Chien Jet Propulsion Laboratory, California Institute of Technology © 2013 California."— Presentation transcript:

1 Campaign Types used in Rosetta Case Studies Steve Chien Jet Propulsion Laboratory, California Institute of Technology © 2013 California Institute of Technology, all rights reserved. Material in this presentation should be considered under U.S. export control is released to the ESA Rosetta team as per existing TAA.

2 Campaign Templates Four basic campaign types represent pretty much all campaigns in Rosetta Escort and pre- landing modelled thus far. – (Outer repetition) Inner Repetition – (Outer repetition) Inner Cumulative Duration – (Outer repetition) Inner Timing Offset (multiple Rules) – Cumulative Monitoring

3 Example, Escort April 2013/vJuly2013 Campaign NameOuter RuleInner Rule ALICE inner coma for noble gasRepeatcumulative ALICE Mapping of CO in inner comarepeat ALICE search for CO extended sourcerepeat ALICE investigation of ice rich/activerepeat Alice grain composition investigationRepeatcumulative Alice detection and mapping of CO source regions Repeatcumulative Alice great circle scanRepeatTemporal COSIMA Exposure (from Current Escort)cumulative … Source – – Use as credentials – Scenario E-M03-M04-C

4 Example, MTP8 E2E Campaign NameOuterInner COSIMA EXPOSEcumulative COSIMA target analyzerepeat MIDAS analyzerepeat MIDAS exposecumulative Rosina Gas Dyncumulative Rosina Monitorcumulative Giada MonitorTemporal Miro LZ (dusk, dawn)repeat Virtis CO2 Abundancerepeat … Source: JPL-E2E-Nov07

5 Campaign Files The campaign definition file(s) are identified by their header XML definitions declaring a CampaignDefinitionSet as indicated in the below sample file header. … …

6 Campaign Definitions Campaigns are made up of scheduling rules, which indicate to ASPEN/RSSC how to satisfy campaigns. Each rule must have its “minimum satisfaction” criteria met to be satisfied Every rule in a campaign must be satisfied for a campaign to be satisfied. Campaign status for each scheduling run is summarized in a table at the bottom of the GUI.

7 Campaign Definitions Campaigns have temporal extent – Scheduling rules are only applied within the temporal extent of the campaign Campaigns have priority – This indicates the order in which ASPEN attempts to satisfy campaigns – Note this is “scheduler priority” not “science priority”

8 Example Campaign Scheduling Rules Simplest type of rule is a simple repeat.

9 Example simple repeat repeat observation 201 while repetition :00:00 003T00:00:00 001T00:00:00 In English, this scheduling rule will attempt to schedule observation 201 up to 56 times, with a 12 hour to 3 day separation in between observations, and a preferred separation of 1 day. Note Min and max are “if this is violated, I don’t want any, i.e. give up! In this case it means if I cant schedule one for 3 days, just give up on the the rest of the campaign, so this should be a HIGH number. Likewise MIN should be LOW. Instead use preferred separation to get desired separation

10 Avoid Rules These indicate that one type of activity and another type of activity are incompatible – Note ASPEN may infer that two activities are incompatible in other ways, such as s/c or instrument state, pointing, resource usage, …

11 Example Avoid Rule avoid observation 201 while observation This scheduling rule indicates that – observation 201 (MIRO limb to limb scan for gas distribution) cannot overlap – observation 9004 (Engineering OCM).

12 Result – Simple Repeat These rules end up with a lot of observations scheduled about a day apart.

13 Cumulative Duration This type of rule schedules observations to achieve a cumulative observation time.

14 Example – Cumulative Duration repeat observation 203 while repetition :00:00 04:00:00 12:43:00 12:44:00 12:43:00

15 Nesting rules Rules can be nested to height (depth) 2. This is done by specifying the action in the “outer rule” to be another rule, which is indicated by the ruleID of the relevant rule (must be within the same campaign*).

16 Example - Nesting MIRO Raster Scan 100 repeat observation 203 while repetition :00:00 12:43:00 12:44:00 12:43:00 repeat rule 1017 while repetition T00:00:00 056T00:00:00 028T00:00:00

17 Nesting Example Rule 1017 is the inner rule. It highlights the “cumulative duration” rule type. It attempts to achieve a cumulative observation time of 12 hours, 44 minutes, while using 2-3 observations with an observation gap of no more than 4 hours. This rule is attempting to schedule for as close to a complete uninterrupted nucleus rotation. However the engineering activities: navcam, WOL, OCM, allow gaps of at most 6.5 hours, therefore some interruptions will occur. Due to the outer repeat rule, these observations scheduled by the inner rule will be repeated a number of times with separation as indicated in the outer rule. We can see these observations in the schedule below.

18 Linking Start and End times Finally, we illustrate yet another nested rule combination, a great circle scan. In this case the entire circle (360 degrees) observation has been broken into three parts because in a single block it would take 10 hours + slewing which is longer than the gaps in between engineering activities. Here we illustrate how the rule schedules the three parts of the observation close together. Rule 1002 schedules the longest part of the observation – the anti-nadir portion of the observation. Because the whole circle is desired to be completed weekly, the scheduling rule for this observation indicates scheduling 8 times preferred (since for an 8 week scheduling horizon), with a min and max of 4 and 12. Likewise the preferred separation is one week (7 days) with a min and max of 3.5 and 14 days. Rule 1030 is for the first near nadir segment. This rule indicates that we should schedule this observation once, and within 7 days of the anti-nadir segment. More specifically, using the “start when start” construct, the start time of this near nadir segment should be no earlier than 1 week before the start of the anti-nadir segment (indicated by the -7 day minimum separation) and the start time for this near nadir segment should be no later than 1 week after the start of the anti-nadir segment (indicated by the +7d maximum separation). Furthermore, the start time of the near nadir segment should be as close as possible to the start time of the anti-nadir segment (indicated by the 0:00 preferred separation). Importantly Rule 1041 indicates that for we need to apply rule 1030 to every condition (e.g. there should be a near-nadir counterpart for every anti-nadir. Rules 1031 and 1040 define an identical second near-nadir segment, linked identically to the anti-nadir observation.

19 Linked Observations ALICE Great circle scan around S/C X axis 100 repeat observation 101 while repetition T12:00:00 014T00:00:00 007T00:00:00 65 start observation 130 when observation 101 start T00:00:00 007T00:00:00 000T00:00:00 66 repeat rule 1030 while repetition 1 every start observation 131 when observation 101 start T00:00:00 007T00:00:00 000T00:00:00 66 repeat rule 1031 while repetition 1 every

20 Another Linked Example Schedule hardest part (CIVA-P) Schedule others relative – On – Lander Compartment Heating – Secondary Battery – ROMAP – Turn Off Schedule Lander compartment end to start Schedule CIVA-P to WoO and pointing Schedule ROMAP start at end CIVA- P Schedule secondary battery start at end ROMAP

21 Monitoring with Options Schedule default as cumulative duration at high priority with avoid WOL, OCM – Set preferred duration to cover entire scenario length – Repetition = DONT CARE Schedule fill in WOL similarly at lower priority – Ensure that both dont occur via instrument/mechanism state

22 Examples of all of these mlgui/rssc/index.html mlgui/rssc/index.html Use as credentials


Download ppt "Campaign Types used in Rosetta Case Studies Steve Chien Jet Propulsion Laboratory, California Institute of Technology © 2013 California."

Similar presentations


Ads by Google