pgabor's blog

There was a big silence from my side regarding the improvements in the past month... Sorry about that, but do not worry, I am summarizing up everything below now: 😉 In the official repo you can find right now these two classes: Transform Visibility Transform 's basic purpose to provide a DFT (Discrete Fourier Transformation) and an IDFT (Inverse Discrete Fourier Transformation) method which can be used to create visbility values from intensity maps and in the other way around. An example for the usage of the DFT method: Converting an intensity map into visibility values with DFT method You can find more information about the Transform class on the github wiki of the project. And now about the Visibility class. During synthesis imaging the data comes from different telescopes with different distance from each other. As a result of this we can create images with the same angular resolution what we would get by using a telescope with the size of what is t

In the past two weeks I got to know to SunPy. I learned about the modules (especially about SunPy Map and Sunpy IO) which will be important this summer. Besides that I spent time with understanding some IDL codes what can be used as a model for the first implementation of the proccess. We have our new repo here: https://github.com/sunpy/xrayvision At the moment it is empty (besides the module template), but soon this is going to change. The first update will be a data structure which can represent the visibilities. For more info visit the issue . Stay tuned!

I am pleased to inform you  this summer I am going to work on as part of SOCIS 2017 to create a synthesis imaging library for SunPy. It will make it possible to create interpretable maps in cases when the base lines are not following a regular pattern. This will be the main focus of the library. You can find more details about the topic in this article . The upper link contains the reference for the first algorithm (CLEAN) what I am going to implement. Currently I am playing around with the little aspects of this task and I try to come up with a good concept how to actually implement it. I spend most of my time reading about the background. My little bit "more technical" proposal for this summer can be found here at github . And at the end, I would like to thank for the SunPy community and ESA that I can participate in this program this summer. I hope my work is going to reach the expectations :) So keep tuned! :D

Update 1: Google Play still not has the newest version, but it is incomming in the following days Update 2: There is an open beta version now, you can get it from here from  Google Play . Marble Maps has the following features: Map Marble Maps uses OpenStreetMap 's map Wondering around on the map You can move the map with one finger by dragging the map with it It will increase the zoom if you touch double times fast to the map You can also zoom with two fingers (only supported on multitouch devices) Handling your position You can check your position on the map You can check the distance and direction to your position when your position is not visible You can center the view to your position Routing You can plan routes via interactive placemarks, you have to search for something and after that, you can use the result as a waypoint Also, you can modify the route instead of the interactive waypoints with the route editor which is available from

In the previous month I worked on compiling Marble widget to Android. It was a long and hard road but it is here: (I shot this screenshot on my phone) The globe can be rotated, and the user can zoom with the usual zooming gesture. Here is a short video example: https://www.youtube.com/watch?v=h0i75ryWdgY The hardest part was to figure out, how to compile everything with cmake instead of qmake and Qt Creator. There are some very basic things what can sabotage your successfully packaged and deployed app. For example if you did not set a version number in cmake for your library... As you maybe know Marble also uses some elements of QtWebKit, but this is not supported on Android. So I introduced some dummy classes to substitute these (of course, not in their useability) to be able to compile Marble for Android. You can find here step-by-step instructions, how to compile Marble Maps for Android: https://techbase.kde.org/Projects/Marble/AndroidCompiling The n

First, I would like to announce, I have been chosen as a Google Summer of Code student and my task is to provide a working version of Marble on Android at the end of the summer. This is a very important for Marble, because Marble currently only available on Desktop and on same rare mobile platforms (Maemo, MeeGo) but on the most widespread platform (Android), not. It is very sad because it is more and more common in education systems that they use TVs, tablets and smartphones with Android so they can’t use Marble as an educational tool. The supported Android platforms will be Android v2.3.3 (API level 10) and higher, because it will be ported with Qt for Android. The work has been started. Stay tuned...