Esse é o Objeto de Hoag, uma galáxia curiosa do tipo anelar: seu núcleo é rodeado por um anel de estrelas, gás e poeira. Sua origem é um mistério, pois galáxias anelares são formadas quando uma galáxia atravessa a outra. Nesse caso não há nenhuma galáxia nas imediações que possa ter feito isso. . This is the Hoag’s Object, a curious galaxy in the the shape of a ring: its nucleus is surrounded by a ring of stars, gas and dust. Its origins remains a mystery, as other ring galaxies are formed when one galaxy passes through another galaxy. In this case, there is no candidate for the bullet galaxy in the vicinity. . Credit: NASA . #nasa #hubble #hubblespacetelescope #telescope #telescopio #astronomia #astronomy #ring #anel #galaxy #galaxia #space #espaço #mistery #misterio #hoag #astrogram #observatoriog1 #bullet #alvo #target
How much is known about Neptune's atmosphere, more precisely about "raining diamonds"?
The atmosphere of Neptune is, in many ways, similar to that of Uranus. However, its dynamics are presented in a complex configuration of strong winds that sweep the planet, besides the formation of cyclonic storms and clouds, with clearly visible visual characteristics.
The upper atmosphere of Neptune is made up of 79% hydrogen, about 18% helium and most of the remaining methane, the presence of which imparts the blue-indigo color of the planet by absorbing the incident red radiation.
The diamond rain on Neptune and Uranus was predicted long ago, because of the pressure inside the planet that could be formed by carbon and hydrogen. But now it was virtually confirmed by an experiment conducted by an international team of scientists, this “diamond rain” was recreated under laboratory conditions for the first time, giving us the first glimpse into what things could be like inside ice giants.
At about 10,000 km below the surface of these planets, hydrocarbon compression is thought to create diamonds. To recreate these conditions, the international team submitted a polystyrene plastic sample to two shock waves using an intense optical laser in the Matter in Extreme Conditions (MEC) instrument, which were then paired with X-ray pulses from Linac Coherent Light Source SLAC (LCLS).
Polystyrene is made from a mixture of hydrogen and carbon, key components of the general chemical composition of the ice giants. In the experiment, the team was able to see that almost all of the carbon atoms in polystyrene were embedded in small diamond structures up to a few nanometers wide.
However, in Uranus and Neptune, scientists predict that diamonds would become much larger, perhaps millions of carats by weight.
2°image: (This false color photograph of Neptune was made from Voyager 2 images taken through three filters: blue, green, and a filter that passes light at a wavelength that is absorbed by methane gas. Thus, regions that appear white or bright red are those that reflect sunlight before it passes through a large quantity of methane). 1°image, 3°image & 4°image.
Here are two links if you want to read about it: Click here and here.
Hi, do you know any resources to start learning coding, preferably for free? Ty!!
Hiya! ✨ Yeah, I’ll see what I can find! However! Online courses often have a build in a code editor. Don’t. Honestly, do not. Get a full software and install it, don’t be restricted to just an online code editor, even on a basic level. First of all decide what language you want to start learning. For complete beginners, I’d recommend Python or C.
💡 codeacademy (this I’ve tried myself and yep, it’s really well written and good for beginners; it doesn’t have many courses tho) 💡 programmr.com 💡 codeavengers💡 code.org💡 Bucky’s wonderful tutorials (these are amazing! I’ve only done the c++ ones, but they were really well explained and included stuff like installing a software as well!)
And now here are some “tools” to use while programming:
🔌 stackoverflow - biggest platform there is; you can ask them anything, but it’s probably been asked before so try looking on it at first🔌 cppreference.com - has all the information about c++ built in libraries, functions, variables and anything you’ll possibly need 🔌 python visualizer - helps you visualize code if you don’t have a compiler on your laptop - they also have other languages🔌 learnpython 🔌 python tutorial🔌 game development with pygame - do something FUN! It’s not that hard, just try it That’s about it! Hope this helps! x
SpaceTime 20190503 Series 22 Episode 34 is now out
SpaceTime covers the latest news in astronomy & space sciences.
The show is available as a free twice weekly podcast through Apple Podcasts (itunes), Stitcher, Google Podcast, Pocketcasts, SoundCloud, Bitez.com, YouTube, Audio Boom, your favourite podcast download provider, and from www.spacetimewithstuartgary.com
SpaceTime is also broadcast coast to coast across the United States on Science360 Radio by the National Science Foundation in Washington D.C. and around the world on Tune-In Radio.
SpaceTime daily news blog: http://spacetimewithstuartgary.tumblr.com/ SpaceTime facebook: www.facebook.com/spacetimewithstuartgary SpaceTime Instagram @spacetimewithstuartgary SpaceTime twitter feed @stuartgary SpaceTime YouTube: https://www.youtube.com/c/SpaceTimewithStuartGary
Today’s stories…
First results from ExoMars Trace Gas Orbiter During its first year in orbit the ExoMars Trace Gas Orbiter has made some surprizing discoveries about the impact of the recent global Martian dust storm and an apparent lack of methane in the red planet’s atmosphere.
Dragon spacecraft destroyed in dramatic explosion The first crew Dragon two capsule which successfully flew to the International Space Station in March has been destroyed in a major explosion at the Cape Canaveral air force station in Florida.
Stratolaunch test flight Stratolaunch has successfully undertaken the first test flight of the company’s behemoth twin fuselage six engine jetliner designed to launch satellites into space.
May Skywatch We tour the night skies of May which play host to the annual Eta-Aquarids meteor shower generated by Halley’s Comet.
Last Wednesday’s show…
New model for Nova explosions Scientists will need to go back to the drawing board to come up with new ways in which powerful explosions – known as novae – can occur on the surfaces of white dwarf stars.
Explaining super-luminous novae Astronomers have discovered that shockwaves generated during nova explosions can dramatically amplify their power and brightness.
NASA’s InSight Detects First Likely ‘Quake’ on Mars NASA’s Mars InSight lander has measured and recorded for the first time ever a likely “marsquake.”
New physics needed to explain differences in the Hubble Constant New observations are showing that differences in how fast the universe is expanding now compared to how fast it was expanding billions of years ago are no statistical accident.
The Science Report Climate change is now threatening the world’s doomsday vault. The world’s second largest colony of emperor penguins almost wiped out. Extreme ocean winds and wave heights are increasing around the globe. A small bone behind the knee, which was once rare in humans is becoming more common. Palaeontologists have unearthed a new species of hadrosaur dinosaur in Mongolia. History revisionists spewing lies and cherry-picked half-truths for racist and political propaganda
SpaceTime Background SpaceTime is Australia’s most respected astronomy and space science news program. The show reports on the latest stories and discoveries making news in astronomy, astrophysics, cosmology, planetary science, galactic and stellar evolution, physics, spaceflight, and general science. SpaceTime features interviews with leading Australian scientists about their latest research. The show is broadcast coast to coast across the United States by the National Science Foundation on Science360 Radio and around the world on Tune in Radio. SpaceTime is available in Australia as a twice weekly podcast which averages around three million downloads annually. It’s hosted on line through Bitez.com on all major podcast platforms. SpaceTime began life in 1995 as ‘StarStuff’ on ABC NewsRadio. Stuart Gary created the show while he was NewsRadio’s Science Editor, evening presenter, and news anchor (a position he held for more than 17 years). Gary wrote, produced and hosted StarStuff, consistently achieving 9 percent of the Australian radio audience share - according to Neilsen ratings survey figures for the five major Australian metro markets (Sydney, Melbourne, Brisbane, Adelaide, & Perth). The StarStuff podcast was hosted by ABC Science on line achieving over 1.3 million downloads annually. Sadly, the popular program was axed in 2015 during ABC budget cuts. Rather than remain with the ABC, Gary resigned to continue producing the show independently and rebranding it as SpaceTime. The first episode of SpaceTime was broadcast on February 8th 2016 and the show has been in continuous production ever since. SpaceTime now reaches an audience almost three times greater that it achieved as StarStuff and continues to grow.
So much advice is heaped upon beginners that it can be hard to know where to start. However, these five practices are the foundation upon which everything else is built. The beginner I have in mind has a basic understanding of how programming works, has written mostly small programs of varying complexity, and is heading off to either a career in the field or committed to excellence for his or own personal projects. There is only one truly foundational activity in programming: writing code. To be good at it, you’re going to have to write a lot of code. That big body of work can be a vehicle for growth, or an exercise in repeatedly practicing a limited set of skills. To avoid the latter, you need to: Read a lot of code. Specifically, read a lot of code by excellent programmers. Not just good programmers, like the guy down the hall, but excellent ones. Due to the huge amount of open source today, this is easy to do. When I was learning Java, I read code from the Tomcat project and from the CI server, Cruise Control. I’ve read lots of good code since. It might be tempting to look for main() and start from there, but you’re likely to spend a lot of time just reading set-up code and command-line parsing. I prefer to scan the filenames to look for some activity that interests me and then dig into those files. It’s not crucial to understand the whole project or the ins and outs of the entire design, you’ll wear yourself out doing this. Read the code. Look at the comments, see what the authors are doing, and how they went about it. Learn your tools thoroughly. I think the greatest loss of programming time is not in debugging or rewriting code, but in the innumerable seconds lost here and there by developers who don’t really know their tools. I am referring to: the IDE, the language, the build system, and the VCS. Of these, the IDE and the language are by far the most important. You should, after a few weeks of practice, know almost every keystroke combo in the IDE, so that you touch the mouse only when it saves a lot of keystrokes. If you know the keystrokes, you know the commands. If you use the mouse only, you know only menus on which you tend to click on the same one or two entries. Knowing the IDE is pure discipline. Knowing large languages, such as Java or C++, takes more than discipline. They’re huge, as are their libraries. Reading is the best approach, in my view. Read code that uses features you don’t know and you’ll look for opportunities to use them. Books (rather than blogs) are another excellent source. Read about features that are on the periphery of what you use currently, and soon you’ll find the periphery expanding. Knowing the VCS and build systems make you a desirable team member — who doesn’t waste time due of ignorance of important operations. Plan your code before you write it. I think this is the most difficult item on this list. In exchange, it probably delivers the most benefit. I’m not thinking of formal design — at your stage, that’s unlikely to be necessary. But you do need to plan out the code in some manner other than carrying it around in your head. The simplest approach is to write up a small document (I frequently use a mind map): What are the requirements for this code? How will you implement it? What do I need to know that I don’t know now? What are the objects I will need or need to create? And write this out. Only then begin to code, you’ll find the code much easier to write, to document, and to get correct. Save your notes — they’re great reference material. Write lots of code and have it reviewed. If your site does not do code reviews, do them yourself. Find the best programmer who’ll give you useful advice in a way that can be heard and understood. Don’t be a pest, but don’t avoid the process because you’re shy, busy, or feel you’re good enough, etc. Code reviews should be part of your programming life. Be creative. Try pair programming with someone more senior than you for an afternoon. The important thing is that you need feedback that you cannot give yourself. Write tests as you code. This advice is perhaps the only controversial item here. It’s not an endorsement of TDD. But it is an endorsement of knowing that your code works in most scenarios it will face. Start with unit tests and exercise new code with edge-case values. For example, does your function work if it is passed a negative value, or the maximum integer size? If not, does it throw an informative exception or just blow up? If not an exception, have you narrowed the range of inputs with asserts? If so, test the asserts. Use the planning you did earlier to write mocks, and then begin testing your new code with objects you still need to write. This will clarify design issues in your current code and the upcoming objects. Save your tests and run them prior to every check-in, so that they can be early warning systems for later code that breaks your current code. There’s a lot more advice and many wise sayings that can be added to this list. But that’s part of the problem: There’s so much advice available that it’s difficult to know exactly where to start. For that reason, I purposely limit my recommendations to just five points. If you apply them with diligence, you’ll soon find two things: You’ll be able to handle progressively larger and more important tasks, and you’ll look back in embarrassment at code you wrote just a few months ago. Both experiences are sure signs of progress. Good luck!
signs of epilepsy to watch for