This is a milestone for Arcsecond ! I am happy to announce that Eric Depagne, currently astronomer at SAAO/SALT has agreed to join his forces to arcsecond.io. His expertise with Python will help a lot on the backend, but I don’t expect him to remain within the boundaries of it!
Moreover, we releases iObserve on the web ! Not as feature-rich as the macOS app yet. But already new features that will belong only to Arcsecond: Night Logs (in prep) and Data !
Well, winter is already there, anyway. So now, iObserve is coming … on the web. #GameOfCurves
For those who don’t know yet, iObserve on the web is called arcsecond.io. You can already checkit out here.
I am very proud of the progresses. But there is a lot to iron out (I had to work on various API endpoints to make it work: /observingsites, /observingruns, /nightlogs, /observations, /users, /telescopes).
But I can’t wait to share with you a (debug) screenshot of the current state of it on my machine. Feel free to spread the word!
I should take the time to annouce a bit more often the releases of my various softwares. But software is a mean of expression by itself, in my humble opinion, when practiced everyday. Don’t you read software? … My blog is my code, and this blog is my secondary blog, talking about the first one.
Anyway, please be aware that arcsecond.io is progressing well. It isn’t still ready for a full-blast communication pushed into professional tubes though. But time will come.
In particular, note the fusion of the Objects and Exoplanets page (which are kinda of object, aren’t they?…). It makes the navigation a lot easier. Moreover, Exoplanet Transits have been also added. Pretty nice. Screenshot below, but judge by yourself directly in this example.
Moreover APIs are slowly maturing, and some API endpoints are now in pretty good shape. Obviously that includes /observingsites, /objects and /exoplanets. I am working full-speed on /observingruns and /nightlogs right now. But /datasets is also pretty nice already (although not yet complete).
To follow all the progresses see my third blog… the arcsecond.io changelog!
In the meantime, I also released a small update of SwiftAA (v2.0.1) to fix some warnings, making sure it is fully compatible with latest Xcode, and applied a small bugfix about the visibility of a special method (that should be kept internal for that matter). Check it out on GitHub!
I am also busy with new adventures for real professional activities this time. But I tend to usually mutualise the benefits, to increase the pace of releases.
Oh by the way, I am preparing a link between arcsecond.io and iObserve ! It’s time for iObserve’s users to submit new observatories and observing sites not in the app but rather in arcsecond.io. They will further be importable inside the app. It will be great. The benefit is that: it is not manual anymore (which is good for me), but is directly accessible and shared with everybody !
I may not update this blog very often, but things keep moving forward!
First, I’ve fixed an important bug in SwiftAA, the iOS/macOS framework of astronomical algorithms. There was a confusion on ecliptic coordinates, which was then propagating to other coordinates, and making impossible to have reliable times of Rise, Transit and Set for celestial objects. What a pity if you couldn’t compute these times with SwiftAA! It is now fixed. Check the release. Even if it takes time, I keep moving forward to reach the 2.0 milestone.
The other updates are about arcsecond.io. I made progresses in many compartments: Datasets, Night Logs, Observing Runs, Profiles. Objects page, Publications etc etc. The new root page now has a Google-like search field. For the exoplanets side, I’m working on something very cool, but it isn’t ready yet (planned for v0.3).
You can check the changes and the improvements brought by every release in the dedicated Changelog page.
As for iObserve, I keep receiving new observatories. Thanks to all. I may consider an update of iObserve to use observatories in arcsecond.io once back from vacations. Better not promise anything though, I know how it goes…
But here is something I am busy with right now: Observing Runs, for which I needed Observing Sites. Looks like a online version of iObserve…
A very first selection of an observing site inside the Observing Runs dashboard.
I know, I am building again a 3-columns-with-topbar layout… But I think this is clearly the most adapted to a pro app like that. More to come soon!
As you certainly know if you read this blog a bit, here and especially here, I am preparing, slowly, a version 2 of my famous app for astronomers: iObserve. One key thing about it are observatories, over and over again. The problem of managing different places, being able to record your own places, possibly sharing them etc, exists since the inception of the app, when it was only in a widget form…
In the course of the years, I’ve developed a lot of things about it and never found it entirely satisfactory. Then came arcsecond.io.
Arcsecond.io was first intended to be the backend for a much lighter iObserve client. But it appears it can solve a lot of things! And the first thing it can solves is to be the one-place-to-go for everything about observatories in the world.
Hence, one of the primary mission of arcsecond.io is to record, store, share, make available all the information about such places.
And the only way to correctly develop, test, bullet-proof the observing sites at arcsecond.io is to build an app, using the arcsecond.swift and SwiftAA sdks. So here it is, for the visible part:
Of course, as soon as it gets ready to edit and display useful things about all observatories, and you can add your own etc, you’ll get your hands on it!
Software is amazing, because it let you create your own world. This is the world as I see it in the future. I learned so much by creating iObserve (over the course of the past years…). And as in science, the main lesson was that I didn’t know much actually…
Hence, since I love challenges, I decided to dive into new questions:
new language for the app iObserve
new architecture for the app
own backend service with specific language
start cloud service with storage and online DB
extract as many macOS components from app into open-source libraries
finally implement dreamed features (night logs, observation simulator…)
I’m sure something is missing…
If someone want to share the bumps ahead on the road, he|she is most welcome.
Clear skies to everyone!
P.S. By the way, arcsecond.io just migrated to Python3…
Dear iObserve users, not many news over here for some time. iObserve 1.5 is still downloaded quite many times every week (reaching 12.5k total downloads!). I can see that some of you send me new observatories. I’ll find some time to create an update of that bunch of new observatories.
Apart from that, I’ve been able to re-compile and re-run iObserve Touch on an iPad with iOS 9.3. And that’s nice, because it wasn’t so easy with the amount of code involved here and there. So maybe I could find some time for a little update as well. It reached almost 6k downloads by itself, wow!
In particular, I am preparing a Swift playground with the best astronomical algorithms in town. The code will be good for developers, for iObserve2, but the Playground could be interesting to teachers! Check it out here the on-going work: https://github.com/onekiloparsec/SwiftAA
Interestingly, this all-code activity is a kind of rest for me. At my startup job, I spend the day interacting with tons of new people (and it’s really great!). So it’s nice to interact with computers a bit. 🙂