Great work! Can you try just saving it again after loading the satellites. That seemed to work for me. Your sitch seems like it did not save the satellites. I suspect a deeper problem.
I looked at his code, and I think he just uses the "active" live group on Celestrak,
I have to admit here, I find the visibility code difficult to read. I need to study it more. The "standard" generally comes from Dr T.S. Kelso's Visually Observing Earth Satellites Volume 3.
VisibilityCalculator::State VisibilityCalculator::calculateState(const Vector3& sat, const Vector3& obs, const TimePoint& t, double el) {
Vector3 sun = getSunPositionECI(t);
double umbra = std::asin(EARTH_RADIUS_KM / sat.magnitude());
double angle = std::acos(sat.normalize().dot(sun.normalize()));
bool lit = (angle < (PI/2.0)) || ((PI - angle) >= umbra);
if (!lit) return State::ECLIPSED;
double sun_el = (PI/2.0) - std::acos(obs.normalize().dot(sun.normalize()));
if (sun_el < (-6.0 * DEG2RAD)) return State::VISIBLE;
return State::DAYLIGHT;
}/**
* getEclipseStatus
* Rference: https://celestrak.org/columns/v03n01/
* @param satposRaw satellite.EciVec3<number>
* @param sunposRaw satellite.EciVec3<number>
* @returns EclipseStatus
*/
function getEclipseStatus(
satposRaw: satellite.EciVec3<number>,
sunposRaw: satellite.EciVec3<number>
): EclipseStatus {
const earthRadius = 6371.0; // km, no scene scaling
const sunRadius = 695700.0; // km, no scene scaling
const satpos = new EciVecOps(satposRaw);
const sunpos = new EciVecOps(sunposRaw);
const dEarth = satpos.length();
const dSun = sunpos.subtract(satposRaw).length();
const theta_e = Math.asin(Math.min(1, earthRadius / dEarth));
const theta_s = Math.asin(Math.min(1, sunRadius / dSun));
const dirEarth = satpos.negate().normalize(); // satellite to Earth
const dirSun = sunpos.subtract(satposRaw).normalize(); // satellite to Sun
const cosTheta = Math.max(-1, Math.min(1, dirEarth.dot(dirSun)));
const theta = Math.acos(cosTheta);
if (theta <= theta_e - theta_s) {
return "UMBRA"; // Earth fully covers Sun center
}
if (theta < theta_e + theta_s) {
return "PENUMBRA"; // partial overlap
}
return "SUNLIT";
}That's not visibility code, it's illumination code. It checks to see if the angular distance of the sat from the sun is bigger than the angular size of the shadow (or if it's on the sunny side), then checks if the sun has set. It's assuming the sat is above the horizon that point, with:
if (r.el < 0) {
color = 4; // RED
state_str = "HOR";
} else {
if (r.state == VisibilityCalculator::State::VISIBLE) { state_str = "VIS"; color=1; }
else if (r.state == VisibilityCalculator::State::DAYLIGHT) { state_str = "DAY"; color=2; }
else if (r.state == VisibilityCalculator::State::ECLIPSED) { state_str = "ECL"; color=3; }
}
Yup, with no concept of "reflection", despite Bob's "It is" in the "BobMcGwier_N4HY" xitter thread linked to above and your gentle "So why didn't you detect those Starlink satellites?" probe which is currently unanswered. Does someone want to reach out to Alpha Phoenix, the guy who made the 2020 youtube vid (id aWpeN3cU17Q) which Bob is using (in the "MickWest" xitter thread linked to above) to support his view that there are no specular reflections from flat-bottomed satellites, he still seems vaguely active on YT? He seems to be smart enough to understand the corner case of the grazing angle instantly. It seems he's prepared to add corrections to his video descriptions, as he's added one already about livability altitudes.
True, but you can't see it unless it's sunlit. In the sat community, it's long been debated what could be expected visibility-wise, and RCS has been tried before and found to be an unreliable indicator of expected visibility. Seems more like you have to actually observe and record them
There's a risk there, as satellite visiblity can vary with the weather and the time of year (different position of the sun)
Too late!
That guy looks like a young me, garage and all
I think Bob went with his initial analysis using the tool he developed, which didn't simulate flares because he wasn't really aware of how they worked. Now I think he's got a better idea and will hopefully update his software.
i guess it's a mix of a number of reasons - they're suspicious of anything Mick does to identify UAPs, but aren't sufficiently knowledgeable to inspect the open-source code. Sitrec can be tricky to use, so they're not willing to spend the time is setting it up for their location, date, time and independently checking their videos. Also the software uses NORAD orbital data, which is a US Government organisation and therefore is also part of the cover up. The software won't show the orbs responding to the telepathic requests from the psionic assets - so it doesn't reflect their reality.
