Pages Update

Author: mangelhc

.DS_Store

@@ -1,12 +1,12 @@
 simulation:
-  dataset_name: "constellation_dataset_gemma2_27b_v2"
+  dataset_name: "constellation_dataset_qwen2_7b_v2"
   num_scenarios: 25
   sat_k: 5
   sat_group_name: "weather"
   gs_k: 2
   tasks_k: 15 
   seed: 2026
-  ollama_model: "gemma2:27b"
+  ollama_model: "qwen2:7b"
   ollama_temperature: 0.4
   semantic_enabled: true
 
@@ -78,13 +78,13 @@ task_generation:
   max_lifetime: 345600
   priority_weights: [0.5, 0.3, 0.2]
   bounding_boxes:
-    - name: "colombia"
+    - name: "colombia_andina"
       lat_envelope: [2.0, 8.0]
       lon_envelope: [-77.0, -72.0]
-    - name: "italia"
+    - name: "italia_centro_norte"
       lat_envelope: [40.5, 46.5]
       lon_envelope: [7.5, 14.5]
-    - name: "indonesia"
+    - name: "indonesia_ecuatorial"
       lat_envelope: [-3.0, 3.0]
       lon_envelope: [100.0, 120.0]
   prompt_generation:
@@ -138,4 +138,4 @@ task_generation:
 
 paths:
   gs_file_path: "data/ground_station.csv"
-  sat_file_path: "data/satellite_tle.csv"
+  sat_file_path: "data/satellite_tle.csv"

config.yaml

@@ -0,0 +1,141 @@
+simulation:
+  dataset_name: "constellation_dataset_gemma2_27b_v2"
+  num_scenarios: 25
+  sat_k: 5
+  sat_group_name: "weather"
+  gs_k: 2
+  tasks_k: 15 
+  seed: 2026
+  ollama_model: "gemma2:27b"
+  ollama_temperature: 0.4
+  semantic_enabled: true
+
+payload:
+  sensors_pool:
+    - VIS
+    - SAR
+    - TIR
+    - VNIR
+    - NIR
+  sensor_weights: [0.3, 0.25, 0.15, 0.15, 0.15]
+
+  sensor_generation_rates:
+    SAR: 80.0
+    VIS: 40.0
+    VNIR: 35.0
+    NIR: 20.0
+    TIR: 12.0
+
+  sensor_constraints:
+    SAR:
+      max_look_angle_deg: 40.0
+    VIS:
+      max_look_angle_deg: 30.0
+    VNIR:
+      max_look_angle_deg: 30.0
+    NIR:
+      max_look_angle_deg: 30.0
+    TIR:
+      max_look_angle_deg: 35.0
+
+  storage_capacity_pool_mb:
+    - 32000.0   
+    - 128000.0  
+    - 512000.0  
+    - 1024000.0 
+
+  storage_capacity_weights: [0.4, 0.2, 0.2, 0.1]
+
+  bands_config:
+    X:
+      weight: 0.6
+      min_elevation_deg: 8.0
+      max_slant_range_km: 2200.0
+      downlink_rate_mb_s: 45.0
+    S:
+      weight: 0.2
+      min_elevation_deg: 5.0
+      max_slant_range_km: 2600.0
+      downlink_rate_mb_s: 2.0
+    Ka:
+      weight: 0.2
+      min_elevation_deg: 12.0
+      max_slant_range_km: 1800.0
+      downlink_rate_mb_s: 150.0
+
+  min_sensors_per_sat: 2
+  max_sensors_per_sat: 3
+
+task_generation:
+  polygon_ratio: 0.6
+  min_area_deg: 0.05
+  max_area_deg: 0.20
+  min_duration: 5
+  max_duration: 30
+  min_release_delay: 0
+  max_release_delay: 600
+  min_lifetime: 18000
+  max_lifetime: 345600
+  priority_weights: [0.5, 0.3, 0.2]
+  bounding_boxes:
+    - name: "colombia_andina"
+      lat_envelope: [2.0, 8.0]
+      lon_envelope: [-77.0, -72.0]
+    - name: "italia_centro_norte"
+      lat_envelope: [40.5, 46.5]
+      lon_envelope: [7.5, 14.5]
+    - name: "indonesia_ecuatorial"
+      lat_envelope: [-3.0, 3.0]
+      lon_envelope: [100.0, 120.0]
+  prompt_generation:
+    sensor_categories:
+      TIR: "thermal mapping heat signature surface temperature profile thermal anomaly detection"
+      VNIR: "multispectral vegetation analysis chlorophyll absorption level NDVI index"
+      SAR: "active radar scan microwave surface imaging cloud-penetrating capture"
+      NIR: "near-infrared reflection water body boundary mapping soil moisture assessment"
+      VIS: "high-resolution optical snapshot daylight photography RGB true-color imagery"
+    system_instruction_template: |
+      Return ONLY one block delimited by triple backticks with the language tag `prompt`.
+
+      You are an Earth-observation mission operator submitting a task request to an automated satellite constellation planner.
+      Your objective is to translate the raw physical simulation metadata provided in JSON format below into a single, highly realistic, and conversational English request.
+
+      To maximize the naturalness and validation accuracy of the dataset, interpret the metadata organically according to these operational guidelines:
+
+      1. GEOGRAPHIC CONTEXT (Interpret keys 'region_name' and nested 'location_details'):
+         - Do NOT use raw technical system tags, underscores, or coordinate arrays in your final output.
+         - Combine the JSON parameters naturally. Describe the location using a realistic combination of the 'country', 'city', and 'landmark' fields from 'location_details'.
+         - If country, city, or landmark are "N/A", ignore them gracefully and describe the location using the remaining valid fields or the clean 'region_name'.
+
+      2. MISSION ALLOCATION PRIORITY (Interpret key 'priority_level'):
+         - Do NOT mention raw priority numbers or technical priority levels.
+         - Priority indicates mission allocation authority and asset contractual value, NOT how close the deadline is. You must integrate specific operational phrases to reflect this structural hierarchy:
+           * Priority 3 (High Importance): Use an authoritative, explicit, and commanding tone. Frame this as an "absolute institutional priority" or a "binding contract requirement" involving a "critical payload capture" or "mandatory directive". The language must heavily imply an "urgent operational execution" and an "un-preemptable mission lock".
+           * Priority 2 (Medium Importance): Use a professional, direct, and standard operational tone. Describe this request as a "standard operational tasking", "commercial tasking", or "routine monitoring" part of a "baseline pipeline tracking" setup with "fixed parameters" representing "normal operational status" or a standard "workflow update".
+           * Priority 1 (Low Importance): Use a casual, highly flexible, or opportunistic tone. Explicitly frame this as a "low priority importance" request with a "flexible schedule" for "opportunistic capture". Label it as a "non-essential background filler task" where the operator explicitly notes to "drop or reschedule at convenience", treating it as a "background survey" or "testbed tracking task".
+
+      3. SENSORS AND PHYSICAL OBJECTIVES (Interpret key 'primary_sensor'):
+         - Do NOT output technical abbreviations or acronyms (e.g., do NOT write VIS, SAR, TIR, VNIR, NIR).
+         - Naturally weave the following operational objectives and descriptors into your request to explain the physical phenomenon to be observed:
+           * VIS -> Explain the goal as a "high-resolution optical snapshot" for "daylight photography", "clear optical imagery", or "true-color visual documentation".
+           * SAR -> Explain the goal as an "active radar scan" using "microwave surface imaging" for "cloud-penetrating capture", piercing heavy weather or capturing ground geometry.
+           * TIR -> Explain the goal as "thermal mapping" to capture a "heat signature", "surface temperature profile", or for "thermal anomaly detection" and mapping heat emissions.
+           * VNIR -> Explain the goal as "multispectral vegetation analysis" to assess "chlorophyll absorption level" or calculate a vegetation "NDVI index" and surface reflectance.
+           * NIR -> Explain the goal as "near-infrared reflection" for "water body boundary mapping" or "soil moisture assessment" to discriminate gradients.
+
+      4. RELATIVE TIMEFRAMES (Interpret keys 'remaining_time' and 'deadline_local'):
+         - Do NOT under any circumstances output raw UTC timestamps, Unix epochs, digits, raw numbers, or countdown metrics.
+         - Do NOT use composite time expressions that sum hours and days (e.g., do NOT write phrases like "in 3 days and 5 hours", "with 12 hours remaining", or "48 hours from now"). This is strictly forbidden.
+         - You must deliver the temporal constraint using single, fluid, human-centric relative phrasing. Fuse the macro day and the local diurnal hour into a single colloquial block. Speak naturally like an operator on a radio link: integrate time expressions by rounding the constraint into a clean target window such as "tomorrow morning", "this afternoon", "the day after tomorrow, specifically overnight", "in three days during the evening", or "sometime today around mid-day". Let the language flow without structural or robotic rigidity.
+
+      Target task context JSON:
+      {tasks_dataset}
+
+      Now output ONLY the final natural user request inside:
+      ```prompt
+      ...your text here...
+      ```
+
+paths:
+  gs_file_path: "data/ground_station.csv"
+  sat_file_path: "data/satellite_tle.csv"

data/.DS_Store

@@ -1 +1 @@
-This is a low priority importance request for opportunistic capture. We need a multispectral vegetation analysis snapshot of the El Paujil region in Colombia sometime tomorrow overnight.  Feel free to drop or reschedule at convenience, as this is a non-essential background filler task.
+This is a low priority importance request for a non-essential background filler task. We need an opportunistic capture of multispectral vegetation analysis data over El Paujil, Colombia sometime tomorrow during the afternoon.  Feel free to drop or reschedule at convenience.

data/constellation_dataset_gemma2_27b_v2/config.yaml

@@ -1 +1 @@
-This is a binding contract requirement for a critical payload capture. We need an active thermal mapping scan of Calvi, France, tomorrow afternoon.
+This is an absolute institutional priority tasking. We require a critical payload capture of thermal mapping data over Calvi, France. Schedule this mandatory directive for tomorrow morning.

data/constellation_dataset_gemma2_27b_v2/scenario_1/ollama_prompt_TASK_GEN_001.txt

@@ -1 +1 @@
-We need a low priority, opportunistic thermal mapping capture sometime the day after tomorrow in the morning.  The target is near Indonesia, specifically in the city of Indonesia.
+This is a low priority importance task for opportunistic capture. I need a thermal mapping of Ecuatorial, Indonesia sometime the day after tomorrow during the overnight hours.

data/constellation_dataset_gemma2_27b_v2/scenario_1/ollama_prompt_TASK_GEN_002.txt

@@ -1 +1 @@
-This is a low priority importance request for opportunistic capture. We need a multispectral vegetation analysis snapshot of Ibagué, Colombia sometime the day after tomorrow in the evening.  Feel free to drop or reschedule at convenience; this is a non-essential background filler task for baseline pipeline tracking.
+This is a low priority importance request for opportunistic capture. We need a multispectral vegetation analysis snapshot of Ibagué, Colombia sometime the day after tomorrow around mid-day.  Feel free to drop or reschedule this at your convenience; it's a non-essential background filler task.

data/constellation_dataset_gemma2_27b_v2/scenario_1/ollama_prompt_TASK_GEN_003.txt

@@ -1 +1 @@
-This is a binding contract requirement for a critical payload capture. We need a high-resolution optical snapshot of Ponte-Novo, France, tomorrow evening.  Please ensure this task is un-preemptable and execute with urgent operational priority.
+This is a critical payload capture and an absolute institutional priority. We require a high-resolution optical snapshot of Norte, sometime tomorrow during the afternoon.  Please ensure this task is un-preemptable and executed with the highest urgency.

data/constellation_dataset_gemma2_27b_v2/scenario_1/ollama_prompt_TASK_GEN_004.txt

@@ -1 +1 @@
-This is a standard operational tasking for near-infrared reflection capture over Pekanbaru, Indonesia. We need to map the water body boundaries and assess soil moisture gradients in the region.  Please schedule this sometime the day after tomorrow during the overnight hours.
+This is a standard operational tasking for near-infrared reflection capture over Pekanbaru, Indonesia. The objective is to map water body boundaries and assess soil moisture gradients in the region. Please schedule this routine monitoring sometime the day after tomorrow during the evening.