Archive for category Helioviewer.org
We have added more options when creating a movie. After you have selected the data and area you want you’ll see the new “Advanced Settings” option in the bottom left hand corner of the movie settings dialog:
If you click on that the dialog will be replaced with the one below. You can now specify the exact start and end times of your movie.
The size drop-down menu allows you to specify the size of the video you want – HD, Full HD, Quad HD or 4K/Ultra HD.
Helioviewer will automatically resize the movie to give you the best resolution video available at the size of the video you request. Helioviewer will remember if you are using the advanced or regular movie settings for making movies.
If you would like any other movie formats included, or if you encounter any problems using this new functionality, please let us know. Thanks for using the Helioviewer Project!
The transition to using the HTTPS protocol broke Helioviewer’s YouTube sharing capability. We tracked down the source of the bug and have fixed it. YouTube sharing has now been re-enabled. Please let us know if you continue to encounter any problems sharing videos from Helioviewer.org to YouTube.
We apologize for any inconvenience caused, and thank you for using the Helioviewer Project.
Helioviewer.org is moving to using HTTPS instead of HTTP. This means that all communications between your browser and helioviewer.org are encrypted. The switch to using HTTPS only will happen on September 30th. An unfortunate side effect of this is that your helioviewer.org movie and screenshot histories will be lost. This is due to security features in your browser, which are explained below.
Helioviewer.org uses the HTML5 LocalStorage property to store your links to the movies on your computer. LocalStorage does not allow data from a regular HTTP page (for example http://htmlui.com) to be accessed by pages served from its HTTPS version (for example, https://htmlui.com, and vice versa. This is done to improve security; for example, you want to isolate values created during a secure session from unsecured sessions. The practical effect of this security is that when we switch to using HTTPS, the histories created when helioviewer.org was using HTTP cannot be accessed by your web browser when helioviewer.org starts to use HTTPS. So your movie and screenshot histories will not be viewable in helioviewer.org.
The switch to using HTTPS does not affect any movie links to helioviewer.org. If you have a link for example, http://helioviewer.org/?movieId=KSJd5 , then the server will automatically switch to using the secure version, https://helioviewer.org/?movieId=KSJd5 . Please make a note of any movie links you want to keep a hold of.
We apologize for any inconvenience this may cause. If you have questions concerning the change from HTTP to HTTPS, please let us know.
The Helioviewer Project is pleased to announce that Helioviewer.org 3.1 is now available. This new version of helioviewer.org adds two new features, an event timeline and improved YouTube movie browsing.
The event timeline allows you to pan backwards and forwards in time, and zoom in and out, browsing what happened and when it happened on the Sun. It is accessible via a tab at the bottom of the viewer window, and works in the same way as the image timeline.
The YouTube movie browser now allows you to see if any shared movies include the date and time you are looking at. It’s a way of finding out what other people have seen on the Sun.
This new feature was suggested by a user of helioviewer.org. If you have a suggestion of how to improve helioviewer.org, please email us at email@example.com.
Thanks, and we hope that you enjoy this new version of helioviewer.org.
Due to some necessary infrastructure upgrades, users of Helioviewer Project clients will experience an interruption in the availability of AIA images, HMI images, and HEK feature and event data, over the weekend of 27-28 September. We apologize for this interruption. Data from all other instruments should update as normal. Normal service with respect to AIA, HMI and the HEK will be restored as soon as possible.
Full Helioviewer Project services originating at NASA – helioviewer.org, JHelioviewer and the Helioviewer API – are now back up and running. Over the next couple of days we will be backfilling in missing data from the period October 1 – 17, 2013. Thanks to our colleagues at the Space Influences Data Center (SIDC) at the Royal Observatory of Belgium for providing Helioviewer services in that period.
JHelioviewer users who edited their user profile files to use the ROB server can switch back to using Helioviewer services at NASA by removing the edits
We thank you for your patience over the past couple of weeks.
The Sun has many different features and events of great scientific interest. It’s useful to be able to catalog those features and measure their properties. By doing so, we can build up more knowledge about the Sun.
The Heliophysics Event Knowledgebase (HEK) is one such catalog. The HEK collects and stores information about many different types of solar feature – active regions, flares, etc, from many different sources around the world. Each solar feature and event can be detected in different ways. Some features and events are detected by people looking at the data, and some are detected by specialized computer vision algorithms.
We’ve taken the information in the HEK and designed a simple interface to allow you to find out what features and events occurred on the Sun at any given time. We’ve organized the information in the HEK by feature/event. You may need to reload helioviewer.org to get the latest version which includes the HEK.
The numbers at the end of each line tell you the total number of features/events of each type on the Sun at that time. You can select any combination of features and events you want (green tick marks), or you can select none. If you’ve selected a particular type of feature/event but the text is faded out, this means that there are none of those particular feature/events at the time you’ve requested. If you browse forward and backwards and time and those feature/events are in the HEK, helioviewer.org will display them.
We then break down the total number of features/events by feature recognition method. We do this because different feature recognition methods can give different results for the same feature/event type. You can select any combination of the available feature recognition methods, or you can select none. For example, the active regions on the Sun at this time were detected using two different feature recognition methods:
Here’s a typical view of some AIA 304 data with the HEK features and events overplotted.
Each of the marker pins corresponds to the feature/event detected by a feature recognition method. Clicking on them pulls up much more information on each individual event. Each of the marker pins also has a small label attached to it with an important piece of information concerning that feature/event. We’ve also extended the movie and screenshot capability so that your selected feature/event markers and labels appear in any movies and screenshots you make.
Finally, in the bottom left-hand corner of the viewer window you’ll see a small image of the Earth. This is the size of the Earth on the same scale as the solar and heliospheric images. This also appears in movies and screenshots of the Sun. Full information on using helioviewer.org can be found by clicking the help link at the bottom of the helioviewer.org webpage.
The HEK is the result of much work by many different people around the world. We are happy to be able to present data from this great solar and heliospheric resource in Helioviewer.org.
We are currently experiencing some technical difficulties with our main Helioviewer server. While we work on fixing it, we have moved all helioviewer.org services over to our backup server. All normal helioviewer.org services should be operating nominally. Please contact us if you notice anything amiss with helioviewer.org. JHelioviewer services are currently not operational, but we hope to have these up and running as soon as possible. Near real-time AIA and HMI images should be available as usual; streams of images from SOHO, STEREO and PROBA2 should be back to near real-time within 24 hours.
We apologize for the interruption to Helioviewer services, and we thank you for your patience.
Alongside of our coverage of the last Transit of Venus that most of us will get to see (the next one will be in 2117 for those of you who are particularly ambitious!) we are also launching a new online discussion forum: community.helioviewer.org.
Here, users can share interesting features and events they find and get help identifying solar phenomena. In addition to forums on topics such as “transits and eclipses” to “coronal mass ejections,” we also have other sections including “solar physics” and “heliophysics” for anyone interested in learning more about the science that goes on behind the pretty pictures and movies.
Check it out and let us know what you think!
Helioviewer.org and JHelioviewer will be unavailable on Tuesday, May 29 from approximately 14:00UT – 16:00UT for planned server maintenance. We apologize for any inconvenience this may cause.
A new version of Helioviewer.org has been released including better movie customization, support for embedding Helioviewer.org in remote sites, and a number of performance and bug fixes.
Support has been added for embedding Helioviewer.org into third-party websites, and JSONP support makes it easier for new versions of the front-end to be created which interact with the main Helioviewer.org back-end. Similarly, the front-end has been rewritten to allow for easier creation of custom front-end clients without having to re-implement a tiling system, etc.
The back-end movie queuing system has been ported from Ruby to PHP to allow for better integration with the rest of the back-end, and the movies table structure has been modified for improved time estimation and similarity searching. Additional options (frame-rate and movie length) are offered to allow users further control over the movies they create and the duration option has been moved to a more obvious location.
Let us know what you think, or if you have any suggestions. Feedback is always welcome.
Helioviewer.2.3.0 includes several new features to give users more control over how the site behaves. Let us know what you think, or if you have any suggestions. Feedback is always welcome.
* JSONP support
* Added option display date from last visit when returning to Helioviewer.org
* Added setting to automatically update images every 5 minutes
* Added support for embedding Helioviewer.org in other websites
* Added support for specifying frame-rate or duration during movie creation
* Added support for PROBA-2 SWAP data
* Created an installer diagnostic script
* Added support for tracking custom events in Google Analytics
* Movie and screenshot selection rectangle preserved during visit
* Data availability information included in getDateSources response
* Fixed bug #691356 JPX Summary file does not exist
* Fixed bug #783497 Port Helioqueuer to PHP
* Fixed bug #903360 Error occurs for certain layer orders when attempting to create AIA/LASCO
* Fixed bug #925542 The minimum width of the display window is too big
* Fixed bug #624857 After clicking “clear history” unfinished requests are still processed, and download links displayed
* Fixed bug #885795 Add image attribution to about dialog
* Fixed bug #888269 Attempt to normalize movie frame-rate instead of duration when possible
* Fixed bug #909795 Normalize date strings for API requests
* Fixed bug #909897 Mark movies that have not finished in less than x hours as Error
* Fixed bug #930628 Improve movie creation time estimation
* Fixed bug #942547 Validate value for dsun before attempting to process in front-side
* Fixed bug #609219 API should return an error message when an invalid parameter is specified in a request
* Fixed bug #783481 Report mouse coordinates immediately upon activation
* Fixed bug #787744 Add a checkSettings method to the UserSettings class to verify user settings integrity
* Fixed bug #876707 Included creation_time in FFmpeg metadata for mp4/webm movies
* Fixed bug #789515 Reduce filesize of WebM movies
* Flowplayer (3.2.7 => 3.2.8)
* jQuery (1.7.0 => 1.7.2)
* jQuery UI (1.8.16 => 1.8.18)
* jQuery.JSON (2.2 => 2.3)
* jQuery imgAreaSelect (0.9.5 => 0.9.8)
What happened? Well, there was an eruption on the back side of the Sun, that caused a propagating disturbance in the solar atmosphere. that appears to have triggered a prominence lift-off on the front-side of the Sun. This is a great example of how the high cadence, continuous observations from Solar Dynamics Observatory give us a much better view of how distant parts of the Sun can physically influence each other. We liked this event so much we made and uploaded some movies of our own. The lower cadence of these movies allows you to see the swaying of coronal material in response to the disturbance from the initial eruption.
YouTube and Helioviewer.org user sedge2002 found another coronal cavity. This one was on the Sun late 2011 to early 2012. It appears towards the end of this movie, at around 30-45 degrees clockwise from the north pole of Sun, above the limb:
Thanks to sedge2002 for making this movie and sharing it with other users of Helioviewer.org. As the movie demonstrates, coronal cavities do occur, and so the one you may have earlier in the week, whilst a great example of a coronal cavity, is definitely not unique. What is a coronal cavity? Let Dr. Alex Young of the The Sun Today tell you:
Helioviewer.org and JHelioviewer will be unavailable on Thursday, March 15 from approximately 14:00UT – 16:00UT for planned server maintenance. We apologize for any inconvenience this may cause.
We are very pleased to announce that Helioviewer Project services are now back online.
This means that Helioviewer.org, JHelioviewer, and other applications that use Helioviewer Project services are now available and should be working as before. If you encounter any problems with any of our services please let us know. We are currently filling in missing data from 2011/08/05 through to 2011/09/16, and we ask for your patience during the next couple of weeks as we fill in the gaps. If you notice any gaps, please let us know, as we are eager to have as complete a record of solar activity as possible.
We do apologize for the interruption in service. This was caused by two distinct and unfortunately simultaneous hardware malfunctions on our server that took a long time to repair. We are looking exploring options that will ensure such a long break in service does not happen again. We are back now, and we hope you continue to explore your heliosphere!