Exploring the software that flies SpaceX rockets and starships

Post by noir_lord » Tue, May 11, 2021, 1:03 PM UTC

ilrwbwrkhv wrote: post #42

skizm wrote: post #36

Earlier quoted context omitted.

Makes sense from a financial standpoint too since game devs are known to be passionate enough to accept lower salaries if they can work on cool stuff. Not necessarily knocking it (not my preference), but it matches exactly what I hear from people that work there. The recruiters even say the pay is low, but you'll have "SpaceX" on your resume so it's worth it.

Also it's world changing work. The best you can do at other faang companies is click ads.

Post by BigMajestic » Tue, May 11, 2021, 1:06 PM UTC

yetihehe wrote: post #40

galangalalgol wrote: post #25

Earlier quoted context omitted.

Unlikely, they talk about 50hz and 10hz tasks. Real time OS often allow you to create threads that run at a given rate and must comolete. Like the 50hz task would have 20ms to complete.

Very likely: while(true) { ...[50hz tick tasks] if(tick%5==0) { ...[10hz tick tasks] } wait_for_next_tick(); tick++; }

Post by galangalalgol » Tue, May 11, 2021, 1:07 PM UTC

yetihehe wrote: post #40

galangalalgol wrote: post #25

Earlier quoted context omitted.

Unlikely, they talk about 50hz and 10hz tasks. Real time OS often allow you to create threads that run at a given rate and must comolete. Like the 50hz task would have 20ms to complete.

Very likely: while(true) { ...[50hz tick tasks] if(tick%5==0) { ...[10hz tick tasks] } wait_for_next_tick(); tick++; }

Post by audunw » Tue, May 11, 2021, 1:09 PM UTC

sandGorgon wrote: post #48

are the 50hz chips manufactured at 50hz ? or are they downclocked to 50hz. why cant you use higher clocked speeds ? like even 500 mhz, etc ? is there something special about 10 and 50hz ?

Post by chasd00 » Tue, May 11, 2021, 1:12 PM UTC

BigMajestic wrote: post #53

yetihehe wrote: post #40

Earlier quoted context omitted.

Very likely: while(true) { ...[50hz tick tasks] if(tick%5==0) { ...[10hz tick tasks] } wait_for_next_tick(); tick++; }

Nope, more likely there are internal CPU timers which emits hardware interrupts on which the tasks are performed