A comet gets destroyed by the sun, data centers endanger the Potomac River, and more science news


The Artemis II astronauts are settling back into life on Earth, but we’re not quite tired yet of hearing about their amazing journey. There’s a new PBS documentary now streaming on YouTube that dives into the Artemis program and the latest efforts to send humans to the moon again. Also this week, NASA shared some awesome images of a comet flying into the sun, the nonprofit American Rivers released its annual report on the most endangered rivers in the US and ESA posted a throwback image of Mars to highlight some interesting changes down on the surface. Here are the science stories that caught our attention this week.

A comet grazes too close to the sun

Earlier this month, a recently discovered comet made a close approach to the sun — but it couldn’t handle the heat. NASA has shared incredible images of the encounter that took place on April 4, showing the comet exploding into dust as it swings around our star. As NASA notes in a social media post, this was “its first and last observed flyby of the Sun.”

The comet, C/2026 A1 (also known as MAPS) was first spotted on January 13 of this year. As it neared the sun, it was observed by a slew of instruments: NASA and ESA’s SOHO (Solar and Heliospheric Observatory) spacecraft, NASA’s STEREO (Solar Terrestrial Relations Observatory) and NASA’s PUNCH (Polarimeter to Unify the Corona and Heliosphere). This allowed for views of its passage from multiple angles. Seen in a narrow-field coronagraph view captured by SOHO, the comet appears to plunge directly into the sun. But, the wide view from NASA’s STEREO shows it actually swinging closely around the sun before breaking apart.

MAPS was one of a family of comets aptly called Kreutz sungrazing comets, and according to Karl Battams, the principal investigator for SOHO’s coronagraph, its destruction occurred likely several hours before what would have been its closest approach.

Potomac named most endangered river in the US

The nonprofit conservation organization American Rivers has released its 2026 report on the most endangered rivers in the country, and data centers play a major role in the status of its top pick. According to American Rivers, the Potomac River is the most endangered in the US due both to the threat of sewage pollution from aging pipe systems and the “unprecedented surge in data center development” in its vicinity.

The Potomac River basin spans parts of Pennsylvania, Maryland, Virginia, West Virginia and Washington, DC. In January, the catastrophic failure of the Potomac Interceptor wastewater pipe in Montgomery County, Maryland dumped hundreds of millions of gallons of untreated sewage into the Potomac River and the Chesapeake and Ohio (C&O) Canal, causing bacteria levels to hit over 4,000 times the safe recreational limit at sites closest to the incident, according to the report. The Potomac Interceptor is over 60 years old, and is just one of many in the region that is at or past the 50-year service life, American Rivers notes.

On top of that, data center development in places like Virginia and Maryland has skyrocketed, which could put a strain on local water and energy sources. Data centers also have potential to cause further pollution to the river.

“The region currently has over 300 data centers and is on track to have a total of about 1,000 centers occupying roughly 200 million square feet of buildings — enough to cover 3,472 football fields — on an estimated 20,000 acres of land,” the report explains. “These facilities pose a significant and growing threat to both water quality and water quantity, yet are being approved without meaningful transparency, regulatory review, and assessment of cumulative impacts.”

The organization is calling for Congress to reauthorize infrastructure funding bills so aging systems can be upgraded, and for regulators in these states to require transparency about data centers’ resource use, along with comprehensive environmental assessments before development plans are approved.

Mars ash: then vs now

An image of a section in Mars' Utopia Planitia showing tan sand on the left side and dark, purplish ash covering the land on the right, creating a stark contrast

ESA/DLR/FU Berlin

The European Space Agency this week shared a look at how a region on Mars has changed since it was observed by NASA’s Viking orbiters way back in 1976. New images captured by ESA’s Mars Express spacecraft show how dark volcanic ash has encroached upon a swath of land in an area known as the Utopia Planitia basin. If you visit the blog post, you’ll find a side by side comparison of images from the two time periods.

It’s a rare example of an observable change on the surface of the red planet that’s occurred over such a short period of time, ESA notes. The agency explains, “The spread of the ash over the last 50 years has two possible explanations: either it has been picked up and moved about by martian winds, or the ochre dust that previously covered the dark ash has been blown away.”


Before you go, be sure to check these stories out too:



Source link

Leave a Reply

Subscribe to Our Newsletter

Get our latest articles delivered straight to your inbox. No spam, we promise.

Recent Reviews


What is a Mapplet?

A Mapplet is an object that can be reused. It will be created in the Mapplet Designer. It includes a set of transformations and allows us to reuse transformation logic in more than one Mapping. Let us understand Mapplets with an example. Consider you have some fact tables which need a series of dimension keys. We can create a Mapplet with a series of Lookup transformations to find every dimension key. We can use this Mapplet in every fact table Mapping instead of recreating the same search logic in every Mapping. As a reusable transformation, any changes to the Mapplet are inherited from every instance of the Mapplet. A Reusable transformation refers to any rule or transition logic defined on the data that will be transformed from source to destination via Mapping, and it can be provided more than once with various methods and logic. it can be used for other transformations.

Mapplet is applicable to mapped data. The source object and the target object will be defined and stored in the database. A logic to be transformed is defined by offering a Mapplet Input that transmits the data from Mapping to Mapplet. After that, a desired Mapplet output transform transmits the Mapplet data to Mapping. So the Input-Output transformations will evolve into cyclic Mapping, transaction logic and reused data without any impact on the data.

Become a Informatica Certified professional by learning this HKR Informatica Training  !

Why Mapplets?

The Mapplets are created to serve two primary purposes:

Whenever we load new data into a table, some space occurs in the source system, and whenever a new transformation is required to be configured on each Mapping. Mapplets are created to prevent this repetition of the creation of the transformation expressions and to end the unwanted space that is formed in the source system. 
On each workflow that is running in the system, a batch id will be formed according to the timestamp of the session using a Mapplet.

Become a Informatica Certified professional by learning this HKR Informatica Training In Hyderabad  !

Informatica Certification Training

  • Master Your Craft
  • Lifetime LMS & Faculty Access
  • 24/7 online expert support
  • Real-world & Project Based Learning

Informatica Mapplet features: 

  • A Mapplet is used to define key data source definitions as well as a source qualifier for providing the data for Mapping.
  • A Mapplet may not have the source definition of the data. Mapplet may accept this data as well from a mapping process via Mapplet input ports.
  • A Mapplet may have several transformations. 
  • The data may be transformed into several pipelines. A Mapplet may include several groups of output ports/groups which may be connected to one another via various pipelines in the Mapping.


Mapplet Components:

For using a Mapplet in Mapping, we must configure the Mapplet for input and output. Apart from the transformation logic we are configuring, a Mapplet includes the following components:

  • Mapplet ports
  • Mapplet input
  • Mapplet output 
Mapplet Ports:

It will be available only in the Mapping Designer. The Mapplet ports comprise the input ports of the input transformations and the output ports of the output transformations.

Mapplet Input:

The Mapplet input may come from the source definition or from the Input transformation within the Mapplet. Several pipelines can be created in a Mapplet. Utilize several source definitions as well as the input transformations or source qualifiers. Alternatively, you can use a mixture of input transformations and source definitions.

Mapplet Output:

The Mapplet output consists of transformation for passing the data through the Mapplet into the Mapping. At Least one output transformation is included in the Mapplet that includes at least one connected port in the Mapplet. Every port connected in the output transformation displays as a Mapplet output port in the Mapping. Every output transformation in the Mapplet is displayed as the output group in the Mapping. The output group may transmit data to several pipelines within the Mapping.

Want to gain knowledge in Informatica BDM? Then visit here to learn Informatica BDM Training!

HKR Trainings Logo

Subscribe to our YouTube channel to get new updates..!

Creation of a Mapplet in Informatica:

The creation of Mapplets involves three steps.

  • First, we must add, connect and then configure the transformations using a transformation logic.
  • Then we need to save the Mapplet using a unique name.
  • Now we can use this Mapplet in the Mapping.
     

When dealing with the Mapplets, mistakes can be avoided by:

  • One of the best ways to avoid mistakes in Mapplets is to comment on every input as well as output transformation that is made in Mapplets so that they will remind us why we have made them.
  • Avoid making modifications to source data datatype, data accuracy or select ports that are connected in the I/O transformation, from the passive to active Mapplet.
     

Follow the rule and guidelines while adding transformations to the Mapplet:

  • When you are using the sequence generator transformation, you should use the reusable sequence generator transformation.
  • When you are using the stored procedure transformation, you should configure the stored procedure Type as Normal.
  • The PowerMart, 3.5 style LOOKUP functions, cannot be included in a Mapplet.
     

Following are the objects that cannot be included in a Mapplet:

  • COBOL sources
  • Normalizer transformations
  • Other Mapplets
  • Target definitions
  • XML sources
  • XML source qualifier transformations
  • Pre and post-session stored procedures
  • Non-reusable sequence generator transformation
     

While reusable shortcuts and transformations in the Mapplet can be used, for protecting the Mapplet validity, use a copy of the transformation rather. Reusable transformations or shortcuts inherit modifications to their original transformations. This could disable the Mapplet and Mapping, which utilizes the Mapplet.

Top 30 frequently asked Informatica Interview Questions !

Informatica Certification Training

Weekday / Weekend Batches

Conclusion:

In this blog, we have learned about Mapplets, why we use Mapplets, Mapplets features, components of a Mapplet and how to create a Mapplet. We hope you found this information helpful!. For more blogs like this, stay tuned to HKR Trainings. 

Related Articles:



Source link