sync

readme.md

@@ -2,9 +2,9 @@
 
 lo-fi star identification
 
-[sky](https://github.com/statespacedev/starid/blob/master/libstarid/sky.h) - generates three-dimensional sky models and two-dimensional images from the nasa skymap star catalog. finds stars near arbitrary points on the sky. [data](https://github.com/statespacedev/starid/blob/master/data/) - the full NASA SKYMAP2000 V5R4 star catalog. [references](https://github.com/statespacedev/starid/blob/master/docs/readme.md) - articles relating to star identification. [about](https://docs.google.com/document/d/1x9GSXXt31vQgR15UQpeO5mcmyg4WYv6mEDPBZ_qwCjY/edit?usp=sharing) - some of the background story.
+[sky](https://github.com/statespacedev/starid/blob/dev/libstarid/sky.h) - generates three-dimensional sky models and two-dimensional images from the nasa skymap star catalog. finds stars near arbitrary points on the sky. [data](https://github.com/statespacedev/starid/blob/dev/data/) - the full NASA SKYMAP2000 V5R4 star catalog. [references](https://github.com/statespacedev/starid/blob/dev/docs/readme.md) - articles relating to star identification. [about](https://github.com/statespacedev/starid/blob/dev/docs/notes.rst) - some of the background story.
 
-[star triangles](https://github.com/statespacedev/starid/blob/master/libstarid/startriangleidentifier.h) - in NOMAD star recognition, there's a chain of triangles and basesides. side2 of each triangle is the baseside of the following triangle. during feedback, these shared side2 and baseside pairs are the path for information to flow backwards, increasing the constraints on the initial triangle baseside and basestar. the name NOMAD relates to how the chain of triangles wanders away from the target star and initial triangle. in SETTLER star recognition, the target star is always star a. star b is a neighbor star. in the inner loops, additional stars c and d are involved. first an abca triangle is formed. this constrains the abside. then for an abca triangle, a sequence of abda triangles are formed, further constraining the abside. when we reach an abda that eliminates all but one star pair possibility for the abside, we've recognized the target star. the name SETTLER comes from the idea that we never move away the target star, we're settling around it.
+[star triangles](https://github.com/statespacedev/starid/blob/dev/libstarid/startriangleidentifier.h) - in NOMAD star recognition, there's a chain of triangles and basesides. side2 of each triangle is the baseside of the following triangle. during feedback, these shared side2 and baseside pairs are the path for information to flow backwards, increasing the constraints on the initial triangle baseside and basestar. the name NOMAD relates to how the chain of triangles wanders away from the target star and initial triangle. in SETTLER star recognition, the target star is always star a. star b is a neighbor star. in the inner loops, additional stars c and d are involved. first an abca triangle is formed. this constrains the abside. then for an abca triangle, a sequence of abda triangles are formed, further constraining the abside. when we reach an abda that eliminates all but one star pair possibility for the abside, we've recognized the target star. the name SETTLER comes from the idea that we never move away the target star, we're settling around it.
 
 20240310 learned a lesson about working on windows laptop - especially for cpp. tracing back over the years, this cpp code has mostly been used on ubuntu. there was a bit of macos thrown in there along the way, involuntarily, but using gcc and things were 'close enough' to ubuntu that the impact was minimal. yesterday, for the first time was really working on cpp code on windows - and got bitten powerfully. windows clion defaults to mingw tools, 'minimal gnu for windows'. build and debug work deceptively well - enough so that the picture gradually builds up that everything's fine. huge mistake. was deep into creating and debugging some relatively intense code. suddenly got an error. this was especially uncool as had been cleaning up to finish for the day and the last change was a trivial nothing.  basically, couldn't believe what was happening, so hammered on it for a while getting more and more frustrated. did seem like a solid error had appeared 'from nowhere' - could detect some slight variation of the particular error, again for seemingly no reason, but was wondering 'what is wrong with windows' - had to just drop it and go for a long walk.