HackerTrans
TopNewTrendsCommentsPastAskShowJobs

sumodm

no profile record

Submissions

Tell HN: Masked email address on Gmail leading phishing attacks

2 points·by sumodm·पिछला वर्ष·0 comments

Apple releasing segmentation/pose for humans and animals, embedding for 27 lang

developer.apple.com
220 points·by sumodm·3 वर्ष पहले·73 comments

comments

sumodm
·2 वर्ष पहले·discuss
FYI: Gukesh is 18 yrs old and the youngest World Champion. He is also the 18th champion, in its 138 years history.
sumodm
·2 वर्ष पहले·discuss
Something along this lines is the real danger. People will understand common failure modes and assume they have understood its behavior for most scenarios. Unlike common deterministic and even some probabilistic systems, where behavior boundaries are well behaved, there could be discontinuities in 'rarer' seen parts of the boundary. And these 'rarer' parts need not be obvious to us humans, since few pixel changes might cause wrinkles.

*vocabulary use is for a broad stroke explanation.
sumodm
·2 वर्ष पहले·discuss
Cruise isn't at fault for the collision with pedestrian, since it was a second order impact. The primary cause being Nissan Sentra and pedestrian. But could cruise avoided the impact and is this how humans react when we drive? Here is the timeline from the report.

  - AV starts moving at -9.2s, after light changes
  - Prediction output shows pedestrian path crossing AV travel lane: -7.7s
  - Pedestrian leaves AV's travel lane: -5.3s
  - Pedestrian pauses at crosswalk : -4.7s
  - Contact b/w Nissan and Pedestrian; -2.7s
sumodm
·2 वर्ष पहले·discuss
> When the light turned green, the Nissan Sentra and the AV entered the intersection. Against a red light, a pedestrian entered the crosswalk on the opposite side of Market Street across from the vehicles, passed completely through the AV’s lane of travel, then stopped mid-crosswalk in front of the Nissan Sentra.

I wonder whether this flagged alarms in Cruise's systems when the pedestrian crossed in a potentially dangerous situation. These kind of 2nd and 3rd order conditions seems particularly hard to train for.
sumodm
·3 वर्ष पहले·discuss
Yes, this seems to be one of the issues. Here is a talk by ISRO Chairman S Somanath at Indian Institute of Science (IISc) about the same and what they added. He goes into details of what went wrong. These are based on my limited understanding. One of the thrusters had an issue and got activated for longer (or may be activation profile of thrusters at its extreme's were different from modeled). They had a narrow landing region selected as final position (even one possible point). So now their control system tried to correct this but the algorithm had a bug and that caused it to be further delayed. At this point the correction required, i.e; thrusters to be activated, was outside the tolerance levels. So finally ended up with 50m/s vertical speed. https://www.youtube.com/watch?v=fZ2sNRP1opY&t=1440s

With new one, they did couple of things. Larger area to be selected for landing based on camera input. Escape sequence to more achievable points, if something like this happens again. They increased the tolerance from 10 degrees to 25 degrees and guessing fixed the bug in code. They also did some smoothening of the trajectory for different phases to make it more continuous. I think they also made other changes in engines among other things and a whole host of testing.