Design and Implement VLA API

[caseyjlaw]

The integration of realfast with the VLA observing system should be a prototype of a general system for third-party systems. As such, a general interface needs to be designed for systems like this.

[caseyjlaw]

Idea came up in a telecon to consider that the realfast system could itself have an API. This would allow tighter integration (faster data rates, maybe?) between CBE and realfast. Then the head node may schedule any kind of work on the cluster. Could be super effective way to define an API, since computing and scheduler are flexible (and written in Python!).

[bryanbutler2]

yeah, i hadn't thought of it this way before and it provides a lot of flexibility. i'm not quite ready to embrace it fully because i haven't thought enough about it, but it's definitely attractive...

-bryan

Casey Law wrote on 9/21/16 16:05 :

Idea came up in a telecon to consider that the realfast system could /itself/ have an API. This would allow tighter integration (faster data rates, maybe?) between CBE and realfast. Then the head node may schedule any kind of work on the cluster. Could be super effective way to define an API, since computing and scheduler are flexible (and written in Python!).

— You are receiving this because you were assigned. Reply to this email directly, view it on GitHub https://github.com/realfastvla/realfast/issues/26#issuecomment-248756763, or mute the thread https://github.com/notifications/unsubscribe-auth/AVNd0nPrVHOUu8l4-XmZdVaQ1Zrcsudpks5qsaoRgaJpZM4KCRfE.Web Bug from https://github.com/notifications/beacon/AVNd0qo2vzKHeqXeRj3-fQla1ScldQsZks5qsaoRgaJpZM4KCRfE.gif

{"api_version":"1.0","publisher":{"api_key":"05dde50f1d1a384dd78767c55493e4bb","name":"GitHub"},"entity":{"external_key":"github/realfastvla/realfast","title":"realfastvla/realfast","subtitle":"GitHub repository","main_image_url":"https://cloud.githubusercontent.com/assets/143418/17495839/a5054eac-5d88-11e6-95fc-7290892c7bb5.png","avatar_image_url":"https://cloud.githubusercontent.com/assets/143418/15842166/7c72db34-2c0b-11e6-9aed-b52498112777.png","action":{"name":"Open in GitHub","url":"https://github.com/realfastvla/realfast"}},"updates":{"snippets":[{"icon":"PERSON","message":"@caseyjlaw in #26: Idea came up in a telecon to consider that the realfast system could itself have an API. This would allow tighter integration (faster data rates, maybe?) between CBE and realfast. Then the head node may schedule any kind of work on the cluster.\r\nCould be super effective way to define an API, since computing and scheduler are flexible (and written in Python!)."}],"action":{"name":"View Issue","url":"https://github.com/realfastvla/realfast/issues/26#issuecomment-248756763"}}}

[caseyjlaw]

Martin's vys protocol naturally allows 3rd parties to connect to correlator without impacting primary operations on the CBE. There is a Python API and some applications being collected at http://github.com/realfastvla/vysmaw_apps