Skip to content

Commit 097b18b

Browse files
committed
bla
1 parent fa0cdf5 commit 097b18b

6 files changed

Lines changed: 2671 additions & 0 deletions

File tree

phi3_model/README.md

Whitespace-only changes.

phi3_model/data/source.txt

Lines changed: 35 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,35 @@
1+
Apollo 11 – Lunar Descent and Moonwalk
2+
3+
As the descent began, Armstrong and Aldrin found themselves passing landmarks on the
4+
surface two or three seconds early, and reported that they were “long”; they would land
5+
miles west of their target point. Eagle was traveling too fast. The problem could have been
6+
mascons—concentrations of high mass in a region or regions of the Moon’s crust that
7+
contains a gravitational anomaly, potentially altering Eagle’s trajectory.
8+
9+
Five minutes into the descent burn, and 6,000 feet (1,800 m) above the surface of the
10+
Moon, the LM guidance computer (LGC) distracted the crew with the first of several
11+
unexpected 1201 and 1202 program alarms. Inside Mission Control Center, computer
12+
engineer Jack Garman told Guidance Officer Steve Bales it was safe to continue the
13+
descent, and this was relayed to the crew. The program alarms indicated “executive
14+
overflows”, meaning the guidance computer could not complete all its tasks in real-time and
15+
had to postpone some of them. Margaret Hamilton, the Director of Apollo Flight Computer
16+
Programming at the MIT Charles Stark Draper Laboratory later recalled: “To blame the
17+
computer for the Apollo 11 problems is like blaming the person who spots a fire and calls
18+
the fire department. Actually, the computer was programmed to do more than recognize
19+
error conditions. A complete set of recovery programs was incorporated into the software.
20+
The software’s action, in this case, was to eliminate lower priority tasks and re-establish
21+
the more important ones. The computer, rather than almost forcing an abort, prevented an
22+
abort. If the computer hadn’t recognized this problem and taken recovery action, I doubt if
23+
Apollo 11 would have been the successful Moon landing it was.”
24+
25+
When Armstrong again looked outside, he saw that the computer’s landing target was in a
26+
boulder-strewn area just north and east of a 300-foot-diameter (91 m) crater, so he took
27+
semi-automatic control. Throughout the descent, Aldrin called out navigation data to
28+
Armstrong, who was busy piloting Eagle. Now 107 feet (33 m) above the surface,
29+
Armstrong knew their propellant supply was dwindling and was determined to land at the
30+
first possible landing site.
31+
32+
Armstrong found a clear patch of ground and maneuvered the spacecraft towards it. They
33+
were now 100 feet (30 m) from the surface, with only 90 seconds of propellant remaining.
34+
Lunar dust kicked up by the LM’s engine began to impair his ability to determine the
35+
spacecraft’s motion.

phi3_model/emissions.csv

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,2 @@
1+
timestamp,project_name,run_id,experiment_id,duration,emissions,emissions_rate,cpu_power,gpu_power,ram_power,cpu_energy,gpu_energy,ram_energy,energy_consumed,water_consumed,country_name,country_iso_code,region,cloud_provider,cloud_region,os,python_version,codecarbon_version,cpu_count,cpu_model,gpu_count,gpu_model,longitude,latitude,ram_total_size,tracking_mode,on_cloud,pue,wue
2+
2025-11-13T06:09:56,codecarbon,c909bc4e-b083-4230-a78a-99ebf1ebeb1e,5b0fa12a-3dd7-45bb-9766-cc326314d9f1,0.08208100000047125,0.013644424732649086,0.16623121955837222,42.5,0.0,10.0,0.01936782330256946,0.0,0.00455692013805555,0.023924743440625004,0.0,Egypt,EGY,,,,Windows-11-10.0.26100-SP0,3.13.5,3.0.8,12,12th Gen Intel(R) Core(TM) i5-1235U,,,,,7.692127227783203,machine,N,1.0,0.0
Lines changed: 3 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,3 @@
1+
task_name,timestamp,project_name,run_id,duration,emissions,emissions_rate,cpu_power,gpu_power,ram_power,cpu_energy,gpu_energy,ram_energy,energy_consumed,water_consumed,country_name,country_iso_code,region,cloud_provider,cloud_region,os,python_version,codecarbon_version,cpu_count,cpu_model,gpu_count,gpu_model,longitude,latitude,ram_total_size,tracking_mode,on_cloud
2+
Recursive RAG Query,2025-11-13T06:09:34,codecarbon,c909bc4e-b083-4230-a78a-99ebf1ebeb1e,142.94884759999877,0.001188882070760797,8.316882338340505e-06,42.5,0.0,10.0,0.0016875667336111143,0.0,0.00039707216333332955,0.002084638896944442,0.0,Egypt,EGY,,,,Windows-11-10.0.26100-SP0,3.13.5,3.0.8,12,12th Gen Intel(R) Core(TM) i5-1235U,,,,,7.692127227783203,machine,N
3+
Recursive RAG Query_f351b95b-3d59-40c2-9d44-ffb9a25be233,2025-11-13T06:09:56,codecarbon,c909bc4e-b083-4230-a78a-99ebf1ebeb1e,0.07393939999928989,6.526370375566776e-07,8.310068383589976e-06,42.5,0.0,10.0,9.271493055622304e-07,0.0,2.172136111108433e-07,1.144362916673941e-06,0.0,Egypt,EGY,,,,Windows-11-10.0.26100-SP0,3.13.5,3.0.8,12,12th Gen Intel(R) Core(TM) i5-1235U,,,,,7.692127227783203,machine,N

0 commit comments

Comments
 (0)