Language Selection

English French German Italian Portuguese Spanish

NASA space probe to slam into comet July 4

Filed under
Sci/Tech

NASA's Deep Impact probe is scheduled to lob a big copper "bullet" into a comet on July 4 to look into the heart of this remnant from the formation of our solar system, scientists said on Thursday.

Impact is expected at 1:52 a.m. EDT (0552 GMT) on U.S. Independence Day.

About a day before the collision, the Deep Impact craft will send a 317-pound (144 kg) copper-fortified impactor toward comet Tempel 1, which will be about 83 million miles from Earth.
The impactor will steer itself toward the comet and the Deep Impact craft will pass about 310 miles away from it and watch the smash-up, the scientists said at a briefing.

Rick Grammier, the project manager for the mission, called this maneuver "extremely challenging."

"It's a bullet trying to hit a second bullet with a third bullet, in the right place at the right time, watching the first two bullets and gathering the scientific data from that impact," Grammier said.

The Deep Impact mission is designed to offer a look under the surface of a comet, where material from the solar system's formation remains relatively unchanged.

Astronomers do not know what kind of impact they will see when the impactor hits: the crater produced on the comet could range in size from a large house to the size of a football stadium. Either way, it will not appreciably change the comet's path.

The crash is expected to eject a spray of ice and dust from the comet's surface and reveal the material beneath it on this Manhattan-sized space rock. At that point, the Deep Impact craft will have about 13 minutes to capture images and data before it weathers what astronomers expect will be a blizzard of particles thrown out of the nucleus of the comet.

There are cameras aboard the impactor and the main craft, and the crash will also be observed by the Hubble, Spitzer and Chandra space telescopes in addition to telescopes on Earth.

Because scientists do not know how bright the impact will be, they can't say whether backyard astronomers will be able to see it. But those with the best chance are those in the western United States and possibly New Zealand.

More information and images are available online at http:/www.nasa.gov/deepimpact.

© Reuters 2005.

More in Tux Machines

PlayOnLinux For Easier Use Of Wine

PlayOnLinux is a free program that helps to install, run, and manage Windows software on Linux. It can also manage virtual C: drives (known as Wine prefixes), and download and install certain Windows libraries for getting some software to run on Wine properly. Creating different drives using different Wine versions is also possible. It is very handy because what runs well in one version may not run as well (if at all) on a newer version. There is PlayOnMac for macOS and PlayOnBSD for FreeBSD. Read
more

Linux Kernel: KPTI, SEV, CBS

  • Experimental KPTI Support For x86 32-bit Linux
    For the Kernel Page Table Isolation (KPTI) support currently within the Linux kernel for addressing the Meltdown CPU vulnerability it's currently limited to 64-bit on the x86 side, but for the unfortunate souls still running x86 32-bit operating systems, SUSE is working on such support.
  • AMD Secure Encrypted Virtualization Is Ready To Roll With Linux 4.16
    With the Linux 4.16 kernel cycle that is expected to begin immediately following the Linux 4.15 kernel debut on Sunday, AMD's Secure Encrypted Virtualization (SEV) technology supported by their new EPYC processors will be mainline. Going back to the end of 2016 have been Linux patches for Secure Encrypted Virtualization while with Linux 4.16 it will finally be part of the mainline kernel and supported with KVM (Kernel-based Virtual Machine) virtualization.
  • Deadline scheduler part 2 — details and usage
    Linux’s deadline scheduler is a global early deadline first scheduler for sporadic tasks with constrained deadlines. These terms were defined in the first part of this series. In this installment, the details of the Linux deadline scheduler and how it can be used will be examined. The deadline scheduler prioritizes the tasks according to the task’s job deadline: the earliest absolute deadline first. For a system with M processors, the M earliest deadline jobs will be selected to run on the M processors. The Linux deadline scheduler also implements the constant bandwidth server (CBS) algorithm, which is a resource-reservation protocol. CBS is used to guarantee that each task will receive its full run time during every period. At every activation of a task, the CBS replenishes the task’s run time. As the job runs, it consumes that time; if the task runs out, it will be throttled and descheduled. In this case, the task will be able to run only after the next replenishment at the beginning of the next period. Therefore, CBS is used to both guarantee each task’s CPU time based on its timing requirements and to prevent a misbehaving task from running for more than its run time and causing problems to other jobs.

Graphics: Mesa and AMDGPU

  • Mesa 17.3.3 Released With RADV & ANV Vulkan Driver Fixes
    Mesa 17.3.3 is now available as the latest point release for the Mesa 17.3 stable series. This bi-weekly point release to Mesa presents several RADV Vega/GFX9 fixes, various Intel ANV Vulkan driver fixes, a DRI3 fix, and random fixes to the OpenGL drivers like RadeonSI, Etnaviv, and even Swrast.
  • R600g "Soft" FP64 Shows Signs Of Life, Enabling Older GPUs To Have OpenGL 4 In 2018
    Most pre-GCN AMD graphics cards are still limited to OpenGL 3.3 support at this time due to not supporting FP64. Only the HD 5800/6900 series on R600g currently have real double-precision floating-point support working right now so at present they are on OpenGL 4.3 rather than 3.3, but those other generations may be catching up soon thanks to the "soft" FP64 code.
  • AMDGPU DC Gets More Raven Ridge Improvements, Audio Fixes
    Harry Wentland of AMD has sent out the latest batch of patches for the AMDGPU DC display code stack. Fortunately it lightens up the DRM driver by about six thousand lines thanks to removing some unused code. Besides gutting out a chunk of unused code, the DC code has a few audio fixes (no word yet on supporting newer audio formats with DC), fixes on driver unload, a "bunch" of continued Raven Ridge display updates, and various other code clean-ups.
  • AMDGPU Firmware Blobs Updated For Video Encode/Decode
    There are updated AMDGPU microcode/firmware files now available for recent Radeon GPUs. The updated firmware files now available via the main linux-firmware.git repository are centered around the video blocks: UVD video decoding, VCE video encode, and the new VCN video encode/decode block with Raven Ridge.

Games: DRAG, Geneshift, Balloonatics and More