Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.


Messages - Daniel Hawton

Pages: 1 [2] 3 4 ... 24
16
News / VATUSA IT - Open Source
« on: May 16, 2018, 03:12:36 PM »
VATUSA is happy to announce that all code for its systems are now open source and viewable by the public.  VATUSA believes that there is no reason for the code to be masked behind closed doors and by opening it up, it opens up the division to changes and suggestions from coders across all of VATSIM and the Flight Sim community.

The projects are as follows [Language or Framework/License]:

vatusa/api - API (v1 and v2) and ULS [Laravel/MIT]

vatusa/current - This is the current frontend and a limited subset of AJAX functions from pages that haven’t been moved to the API [Laravel/CC-BY-NC-SA v4]

vatusa/Dockerfile - Contains base images used by VATUSA’s docker containers [Docker yaml/MIT]

vatusa/exam - VATUSA’s Exam Center integrated with APIv2 [React/MIT]

vatusa/forums - Work in progress of VATUSA’s SMF-forked forums [PHP/BSD License]

vatusa/frontend - Work in progress replacement to vatusa/current [React/GPL]

vatusa/javascript - VATUSA fork of the AirBNB JavaScript Styling Guide [owned by AirBNB]

vatusa/laravel-uls - ULS2A package for use with Laravel 5.x [PHP/GPL]

vatusa/s3monitor - A work in progress to monitor VATUSA’s S3 buckets [Python/MIT]

vatusa/survey - Survey project [JavaScript ES6/MIT]

vatusa/vatdock - VATUSA Web Team’s development environment [Docker yaml/GPL]

vatusa/viz - VATUSA Docker container visualisation [React/MIT] (uses https://github.com/dhawton/docker-viz-monitor for container and node information [Golang/MIT])

The projects can be accessed at VATUSA’s GitHub page at https://www.github.com/vatusa.

Contributions must be submitted via a PR to the “devel” branch of the above projects and must pass a travis build [if applicable] and will be tested before being merged.  No other PRs will be approved.  All code submitted must be licensed with the same license affecting the remainder of the project.  Projects under VATUSA’s GitHub page will be projects maintained by VATUSA, this is not to deter adaptations in other languages but to ensure that projects run and hosted by VATUSA are ones maintained by VATUSA, without increasing workload.

17
The Control Room Floor / Re: ATC Use of Guard (121.500) frequency
« on: May 14, 2018, 12:09:57 AM »
Correct, you do not need to actively monitor 121.5, as the clients passively monitor it.  121.5 transmissions are "broadcasts" and display for all clients (pilot and ATC) that are in radio range.

Ok...  So then is this not a valid method for contact?  Based off the technological implementation of 121.5 transmissions, it would be a valuable resource, as it would display it for a pliot regardless of frequency, so those not monitoring UNICOM could still be reached.

So back to Ken's original question:
is attempting to reach a NORDO pilot acceptable under this "emergency" clause, or should we stick to using the .contactme PM and UNICOM to attempt to reach an otherwise unresponsive a/c?

As far as I am aware, use of 121.5 is restricted by the CoC.  I am unaware of any current VATUSA policy on it.  I know there used to be, but it's no longer listed.

18
The Control Room Floor / Re: ATC Use of Guard (121.500) frequency
« on: May 13, 2018, 06:17:45 PM »
Guard isn't a frequency you specifically monitor. It shows for everyone in radio range whether or not you are monitoring 121.5.

Do you mean it shows everyone in radio range if you transmit on 121.5?

I've never known any part of any radar client that allows us to see other users MONITORING 121.5, but I am familiar with the alert you get when a station in radio range TRANSMITS on it.

If this is the case, you're right, we wouldn't necessarily need to monitor it (nor would the pilots), but why not give it a shot, if neither UNICOM nor the standard contact request has worked, after repeated requests?

Correct, you do not need to actively monitor 121.5, as the clients passively monitor it.  121.5 transmissions are "broadcasts" and display for all clients (pilot and ATC) that are in radio range.

19
The Control Room Floor / Re: ATC Use of Guard (121.500) frequency
« on: May 12, 2018, 09:27:30 PM »
Well, regardless of whether it is ok or not I think the issue would be that the majority of pilots probably aren't monitoring guard to begin with.

If you know an aircraft is on guard, I don't see why you couldn't attempt to reach them that way.

Guard isn't a frequency you specifically monitor. It shows for everyone in radio range whether or not you are monitoring 121.5.

20
General Discussion / Re: Keep Port Open
« on: April 14, 2018, 01:01:49 AM »
The real question is, can we trick it to keeping the port open with a small and simple lightweight application that sends a stream every so often?

No. Operating systems don't allow two applications to bind to the same UDP port.  The easiest method is to port forward or be directly connected to the modem.  There is not a way to have a small application sit and send blank packages over a port bound by vPilot, VRC, vSTARS, vERAM, etc. Windows, Linux, Mac OS, etc. will refuse the connection identifying that the port is already in use.

21
The Flight Deck / Re: E/G floors at 14,500...
« on: April 01, 2018, 04:33:09 PM »
And even in AK their numbers are diminishing.  A good chunk of them are in near GKN.

22
The Control Room Floor / Re: Metering on the Network
« on: March 19, 2018, 01:09:11 PM »
2) The FAA uses software that puts all aircraft inbound to an airport (or an airspace) on a cool timeline that makes it easier on TMU and lets those controllers see immediately where aircraft are bunching up. It would be cool to have some sort of VATSIM approximation of this for events.

I've attempted this, but with such an unknown when it comes to wind aloft and who uses what, where does it change, etc. it was completely unreliable, so I scraped it.

23
It would be helpful for VATUSA to give a blanket waiver to allow any ARTCC that wishes to permit controllers to authorise multiple runway crossings (where centrelines are 1300’ or less) to conduct ground operations in that way.  IRL, my home field is St Augustine (KSGJ) and the cab controllers complain periodically about having to authorise crossings for the two small runways that cross the main taxiway because they are 25 feet too far apart for the multiple crossing instruction!  Now they’ll have to say “cross 6, hold short of 2..... cross 2, continue on Bravo.....”..... MOAR WORDS INDEED!

Perhaps one of the VATUSA folks can sort this so ARTCCs can train accordingly?

Frank

Facilities write procedures, VATUSA approves it.  Not the other way around. ;) Contact your facility for more information.

24
This can't be a VATUSA isolated issue.  Does VATNA/VATUSA have anything to say about it?

VATNA/VATUSA aren't involved in this.  As recommended above, wallop a supervisor so it can be taken care of if such messages are received.

25

In all seriousness i haven't seen these on xsquawkbox. Maybe it is only going through the vPilot client? I might hop onto FSX to see if i see any messages.

Messages are messages. They don't care about the client used, they all work and come out the same.

26
News / VATUSA Privacy Policy Published
« on: February 20, 2018, 01:13:59 PM »
VATUSA has published a privacy policy to inform users what information VATUSA collections and how it is used.

Please see https://www.vatusa.net/info/privacy for more information.

27
The Classroom (Controller Tips) / Re: Mac OS - will it work
« on: February 06, 2018, 07:44:10 AM »
(basically making your Mac Hardware a PC), and not natively running MacOS. From there, you'd run your machine like it is a regular PC.

Just want to point out, it's the same hardware... just with the Apple Tax of 150%+ added to it.  Once they converted from the G# series CPUs to Intel, it was pure 100% PC Hardware.  The only difference now is the case it comes in. ;)

28
General Discussion / Re: What Happens i fail exam can i redo?
« on: January 29, 2018, 10:50:06 PM »
The site should automatically reassign it after some number of days.  The reassignment time is in the failure email, if I recall correctly.

Depends on the exam.  Some exams are not auto reassign.  All rating exams are auto reassigning, some facility exams are set to not auto reassign.


Hiro,
The exam will be reassigned at the top of the hour following the date/time you took the test.  IE, if you took it 1/5/18 at 1:25pm, and there is a 3 day wait, it'll be auto reassigned on 1/8/18 at approximately 2:00pm.

29
General Discussion / Re: New Controller Help Request
« on: January 28, 2018, 05:34:06 PM »
Thank you all for your help!  :D

Another question:  My brother was curious if he could join as well, but he would play on my system; Should he make a brand new separate account?

Yes. It's part of the code of conduct you agreed to on registration that you cannot share your account. I'd recommend going to vatsim.net and heading to the membership help page and submitting a ticket to notify them that you share computers so they don't flag the other account as a duplicate.

30
General Discussion / Re: New Controller Help Request
« on: January 27, 2018, 11:40:07 PM »
P.s. Daniel beat me by a minute!

1 min 47 seconds to be precise ;) lol

Pages: 1 [2] 3 4 ... 24