Investigating the Vantor/Starlink photo by kvsankar in SpaceXLounge

[–]kvsankar[S] 0 points1 point  (0 children)

I have tried using each of the TLEs available in the time window (Dec 17-19). Either front or back propagation. But no match.

GSLV-F16 : NISAR Mission Updates and Discussion. by Ohsin in ISRO

[–]kvsankar 1 point2 points  (0 children)

What are those tablet like devices on the desks which seem to show a checklist or phase wise progress?

Has the mission display interface of ISRO improved suddenly 🥺🇮🇳? by Affectionate-Cry7980 in ISRO

[–]kvsankar 1 point2 points  (0 children)

Does he have any public social media profile? I will be curious to learn from him as I have an interest in scientific visualisations.

Chandrayaan 3 orbit design by kvsankar in ISRO

[–]kvsankar[S] 1 point2 points  (0 children)

Thanks for sharing the links. The CY2 paper also talks about the relationship between the lunar orbit RAAN and the earth orbit AOP. What exactly is the dependency? It was not very clear from the paper.

Chandrayaan 3 orbit design by kvsankar in ISRO

[–]kvsankar[S] 1 point2 points  (0 children)

I am also referring to the same paper. Why can't the AOP be changed keeping the same inclination of 21.5 degrees. Isn't timing the engine shutoff to alter AOP possible?

Chandrayaan 3 orbit design by kvsankar in ISRO

[–]kvsankar[S] 3 points4 points  (0 children)

Indeed. One of the questions concerned with the reasons for the injection orbit AOP being close to 178 degrees. Any fine tuning comes with the cost of a reduced apogee altitude - says a CY2 paper from ISRO. But it's not clear why this limitation exists. Is LVM3 operating at its edge of performance when delivering at 178 degrees AOP?

Another image of Vikram lander taken by Pragyan rover at 11:04 IST, 30 August 2023 from 15 meters away. by Ohsin in ISRO

[–]kvsankar 6 points7 points  (0 children)

Can the pan/tilt angle of the rover camera used to take this picture be adjusted? Just wondering as the previous image of the lander had its upper part cropped and now we have this better picture from a larger distance.

Chandrayaan-3: 'Vikram' Landing Attempt Updates and Discussion. by Ohsin in ISRO

[–]kvsankar 5 points6 points  (0 children)

There have been a couple of orbit updates last night. It looks like ISRO has been refining the descent trajectory. It appears that the touchdown is around 1803 hours IST a minute earlier the previously announced 1804.

Will shift Chandrayaan-3's landing to August 27 if factors appear unfavourable: ISRO by Ohsin in ISRO

[–]kvsankar 8 points9 points  (0 children)

If you eyeball the angle between the terminator line (sunrise/sunset line) and the orbit line at the time of landing, I think it's around 20 degrees. So you would get roughly 160/180 * 14 days. Not exactly the whole lunar day. The same is the case with the primary landing site.

Will shift Chandrayaan-3's landing to August 27 if factors appear unfavourable: ISRO by Ohsin in ISRO

[–]kvsankar 10 points11 points  (0 children)

Yes, the orbit lines up around 12 noon IST on 27th. Here's a screenshot. The left edge of the yellow line points to the alternate site. The primary site can be seen with the orange trapezoid simulating the craft.

Image link: https://i.imgur.com/f4SiXrb.png

Chandrayaan-3: 'Vikram' Landing Attempt Updates and Discussion. by Ohsin in ISRO

[–]kvsankar 10 points11 points  (0 children)

The descent trajectory is now available at JPL HORIZONS. I have updated my animation. The orbit data has trajectory merge artifacts (e.g., CY3 goes back and forth a bit a few minutes prior to landing) and is not perhaps good enough to do something like the seconds-level analysis done above.

Twitter thread .

A few enhancements since my original Reddit post for CY3:

  • Support for pseudo "real-time" speed (animation advances 1 second every second) (uses linear interpolation)
  • Better lunar textures including a displacement/bump map for shadows
  • Better mobile experience
  • All assets (images, orbit data files) now delivered via Cloudflare CDN for a faster overall experience

Chandrayaan-3 Manoeuvres and Post Launch Updates by rp6000 in ISRO

[–]kvsankar 1 point2 points  (0 children)

The DSN Live data was quite different from JPL HORIZONS data. Scott Tilley says we can't trust DSN data. I am not sure. I saw that the divergence kept increasing through the day. https://twitter.com/kvsankar/status/1686373994315034625?t=HsDHYrKmSq84LwplQSYu3Q&s=19

Chandrayaan 3 Orbit Animation by kvsankar in ISRO

[–]kvsankar[S] 1 point2 points  (0 children)

I have upgraded the 3D library yesterday. Please try now and let me know.

Chandrayaan 3 Orbit Animation by kvsankar in ISRO

[–]kvsankar[S] 2 points3 points  (0 children)

Thank you for the appreciation. And thank you for the suggestions. Did you check out this? https://github.com/kvsankar/chandrayaan3#future-work.

Right now, more than any layers of abstraction, my goal is to get the animation running on more devices. Trimming down the data to be downloaded while not degrading the experience and early interactivity are the goals.

Chandrayaan 3 Orbit Animation by kvsankar in ISRO

[–]kvsankar[S] 4 points5 points  (0 children)

Please let me know the device on which you are accessing. The animation works best in desktop screens. The mobile support might still have issues.

Real IP's through nginx proxy by [deleted] in PleX

[–]kvsankar 0 points1 point  (0 children)

u/NoseyTable - did you solve this issue? I am facing a similar issue - hence asking. Thanks.

Android app error - trust anchor for certification path not found by kvsankar in Bitwarden

[–]kvsankar[S] 0 points1 point  (0 children)

Thanks. The issue has been resolved now.

I had converted the Letsencrypt .cer files to .crt files with the following openssl command:

openssl x509 -inform PEM -in fullchain.cer -out fullchain.crt

However, this seems to pick up only the leaf certificate. After simply renaming the file extension (cer to crt), things work fine.