Here I will configure the files in NOS3
active 2024-03-19 → 2024-03-20 (UTC)
Complete coverage26,584 / 26,584 hourly files (100%) · 2 absent upstream2023-08-15 → 2026-08-26 (UTC)
Events
3
Pushes
0
Pull requests
0
Issues
1
Stars
0
Forks
0
Activity over time
Daily event counts in the loaded window
Line chart, 2 days from 2024-03-19 to 2024-03-20. Pushes: 0 total, peak 0 in a day. Pull requests: 0 total, peak 0 in a day. Issues: 1 total, peak 1 in a day. Comments: 0 total, peak 0 in a day. Stars: 0 total, peak 0 in a day.
- Pushes
- Pull requests
- Issues
- Comments
- Stars
Top contributors
Pushes, PRs, issues, reviews and comments — stars and forks excluded, so this is contribution rather than popularity
| Contributor | Contributions | Pushes | PRs | Comments |
|---|---|---|---|---|
| PapiSenpai | 1 | 0 | 0 | 0 |
Recent activity
Latest issues, pull requests and releases
- Issue#1PapiSenpai2024-03-20 02:16I apologize for asking such a n00b configuration question, but I was recently looking at the NOS3 and wanted to be able to run multiple NOS FSW's/Engines/Apps (to simulate interacting with multiple satellites)...the 42 implementation (that NOS3 uses) seems to tie me to a single instance of the NOS Engine configured through the Inp_NOS3.txt (which seems an extended implementation of the original time driver for 42). I read that as being a NOS Engine per satellite, but since 42 can simulate multi
Totals cover only the window loaded into ClickHouse and count events, not GitHub's lifetime totals — 0 stars here means stars gained during the window, not the repo's star count.