I do know that this course is still offered widely across the US, but maybe not within CS, and maybe not as a mandatory course.
But, bottom line: if you're interested, it's very likely you can take it - you may have to check your school of engineering or applied math department.
It really is a tragedy of the commons with a changing demographic, where DINK are more prevalent that, say, 50 years ago, where most tried to contribute to raising the next generation. But the amount of entitlement still baffles me - where do these people think everyone younger than them comes from? How much time and money do they think it costs to train a human being to be a member of society, of benefit to them!, and why do they just assume it is someone else's duty to provide this to them, free of charge to them?
But you still benefit even from the mere _existence_ of human beings younger than you are (e.g. service, manufacturing, research, medical, etc.). If you think you don't, think about the fraction of people you will interact with in 20 or 40 years that are younger than you will be, or about the innovations you will be using in 20 or 40 years that were developed by people younger than you. Those human beings have to come from somewhere - why do you insist it my obligation to make you that gift, at exorbitant expense of my time and money?
There's a simple word for people with that attitude: freeloader. It's pretty easy to understand:
> I can not image the extra amount of work that get places on people that do not have children...
What you're forgetting is the amount of work required to raise children. That's an externality that is only covered through a social contract, where everyone contributes to a next generation. Why should parents put in the extra work to raise children that, god forbid, would ever do something you benefit from?
What you want is someone else doing the work so that you can just reap the benefits. You're a freeloader, plain and simple (other, less favorable words come to mind).
Unless, of course, you will never in your life use the services or inventions of anyone younger than you. But, somehow, I doubt that - am I right? You just expect those cohorts to just appear out od thin air to your benefit.
Just a few words from the other side of the table: I have the highest respect for students sitting there who juggle college, family, sometimes job, after having worked for a while already.
It’s wonderful to have someone listening because of a conscious decision rather than just following the obvious next step. Interact with your professor, ask questions, I’d hope most will try to be supportive, especially when you’re their age or even older. Best of luck to everyone doing this, it’s amazing.
Absolutely! I’m sure they analyzed for that, but backflow to the opposite direction of the nozzle is quite unintuitive but normal in rarefied flow, with propellant deposition next to the nozzle possible and documented [1]. Just because you point it away from the sensitive stuff does not mean it won’t get there and leave nasty traces.
I don’t think I understand the resolution then, could you explain a bit more? Say, I request data along a 100km line, every 10m. Do I get the same numbers if it’s in the same mesh cell with a sudden change when it’s crossed, or do I get some (bilinear?) interpolation?
1) How does the spatial resolution come into this? Is it constant data all across the 2kmx2km (?) parcel with an abrupt change, or is it interpolated in some way? Can I query the coordinates of the mesh?
2) How 'historical' does it get? How far back can I go with this?
a few things to wrap this up for me, and thank you for your civil answer to a not so civil comment.
1st: I should have made this a 'yes and' rather than a 'no but' comment. It's a well written article with nice illustrations, and you put in the time to do so and share it with the world. Thank you for that!
2nd: Obviously you're right that it's possible to calculate the distance to plane by observing when it passes a certain point and then measuring the time until the sound hits you from that very point.
3rd: My smartassery still stands that "How far behind a plane is its noise?" is a misleading way to frame it - the noise is not behind the plane at all, it's actually significantly ahead of it. But (!), again, I should have made that a 'yes, and' instead, to add a facet to your nice article.
That we can calculate the distance to a lightning to great accuracy (my example in the very first sentence) by accounting for a finite speed of sound only and assuming an infinite speed of light? Yeah, I'm pretty serious that we can neglect that error of some microseconds when concerned with a process that takes many orders of magnitude more.
> The noise is always pointing behind the aircraft or any moving object due to lag.
I don't know what a pointing noise is.
> Light also encodes the direction to an objects past location, even though light is always moving faster than the object.
Yet the light is never outrun by the object, much like the subsonic plane never outruns its noise. However, here, the (fast) noise arrives after the (slow) plane. In your analogy, that would correspond to the (slow) object arriving before the (fast) light.
> " These statements exhibit a fundamental misunderstanding of the phenomenon. It's not that the sound outpaces the aircraft. It's that light from the aircraft (reflected or transmitted, e.g., by landing / navigational lights) travels faster than sound."
Explain to me again how any of that explains why the airplane passes me (and I see it 1e-6s later which seems to be somehow super important to you) before I hear it, even though its sound is traveling towards me much faster than the plane.
I do know that this course is still offered widely across the US, but maybe not within CS, and maybe not as a mandatory course.
But, bottom line: if you're interested, it's very likely you can take it - you may have to check your school of engineering or applied math department.