snip<=-
Hi Paul,
I'm not sure if this would be useful for you or fsxNet. I had been
playing around with the code, and made some updates. It analyzes the nodelists.
The Input Nodelist file has 219 Nodes in it
and a total of 249 non-comment entries.
The list has 1 Zones listed.
1 Region Coordinators listed.
5 Network Hosts listed.
Yes, this would be a great addition to have each week, much like they
post toFido (as far as I can tell?)
The list has 1 Zones listed.
1 Region Coordinators listed.
5 Network Hosts listed.
Could the info be displayed in a different order?
Yup. With the source code, I can do anything with it. :) I was thinking about removing the baud rates, as I think there is only a couple nodes with POTS.
I agree I'd remove
Baud Rate Summary (or, BPS, for the die-hard technocrats):
9600 = 0 ( 0.00 %)
Can you explain to me these / and or how they are calculated?
249 non-comment entries
How would you like it arranged?
It would be good to see the % figures against the admin section, I added inthe PVT one.
Also good to understand what Flags the systems tracks individually, so we could add to this and put in some custom ones, for Onion addresses etc.
It's in there. :)
I think if we us the U. in the nodelist, we could basically do anything
we want
NetStats 4.2(RCS) 24 Oct 2020
INPUT NODELIST FILE : FSXNET.304
File has a Date Stamp of : 10/24/2020
File Size (uncompressed) : 30.38 KBytes.
This looks nice Dan. I think it would also be good to have the local
time thereport was run as well, so if it's generated different times on the same dayyou can tell. Perhaps add that to the header too?
This exercise also got me thinking about ways of using the nodelist to tracknumerically and graphically things like
- number of nodes per net
- week to week stats changes in nets as well as across a zone.
I've got the current RunTime date and time listed now. Although I would think this program would only be run once per week.
- number of nodes per net
That can be added. It wouldn't be too difficult to count each net individually.
- week to week stats changes in nets as well as across a zone.
This is something I'm already working on. The program right now, is also generating a comma delimited file with the information. I still need to update the fields. There could be an addition to the program which could generate numbers over time using that file.
Yep, but can we use U for one thing only? If we wanted to implement
flags notnoted in FTSC docs could those be added to the tool as well. Picking yes, butasking as well :)
I've got the current RunTime date and time listed now. Although I wou think this program would only be run once per week.
Thanks :) Yes, or when the nodelist was updated as well?
That can be added. It wouldn't be too difficult to count each net individually.
I figured not, but it would be an interesting stat to watch ebb and flow.
I can add any fields you want into this program. :)
I'm just curious though, as to how the FTSC has any say in how things
are done here? As long as the nodelist can be processed by software, it shouldn't be a problem what we add to it. I would think that the U
fields would be ignored by any processing, as they are not a consistent source for data.
While the above is intended as a joke, I actually wonder if there is any merit in trying to enshrine timezone data in the nodelist? Probably not asthe messages carry the kludge.
'say in things' - MMmm we'll if we run the nodelist for Fidonet I'd say quitea bit but if it's running in and Othernet zone I'd suggest far less... but Iagree ideally it's going to have flags that legacy software can use andothers that it will ignore. Seems flags have just sorta
evolved over time andsome that stuck got documented in FTSC docs...
While it could be done, I'm not sure there's any reason to. As you said, it's already in the message kludge lines.
Also need to keep in mind, how many systems are actually processing a nodelist? I know that Mystic does, but it's more for sending to nodes
Also need to keep in mind, how many systems are actually processing a nodelist? I know that Mystic does, but it's more for sending to nodesI dont think Ive been actively processing a nodelist for 15+ years.
that aren't set up. I don't think that Synchronet *needs* to have a nodelist set up. BinkD doesn't need it... There may be a few that do use it...
Perhaps something like this...
I think it would be great, if we could plug out the city/country from the nodelist and do some stats based on that too...
So, if there was a standard format in the nodelist, eg: Melbourne_AU
(IIRC mostly it is this way), it would be nice to know the distribution
of where folks are from (country wise).
Also need to keep in mind, how many systems are actually processing a nodelist? I know that Mystic does, but it's more for sending to nodes
I would think any system that wants to send netmail should want to processit.. but yeah take you point on the above...
Also need to keep in mind, how many systems are actually processing a nodelist? I know that Mystic does, but it's more for sending to nodes that aren't set up. I don't think that Synchronet *needs* to have a nodelist set up. BinkD doesn't need it... There may be a few that do u it...
I dont think Ive been actively processing a nodelist for 15+ years.
I think it would be great, if we could plug out the city/country from the nodelist and do some stats based on that too...
So, if there was a standard format in the nodelist, eg: Melbourne_AU (IIRCmostly it is this way), it would be nice to know the distribution
of wherefolks are from (country wise).
I think it would be great, if we could plug out the city/country from the nodelist and do some stats based on that too...
So, if there was a standard format in the nodelist, eg: Melbourne_AU (IIRCmostly it is this way), it would be nice to know the distribution
of wherefolks are from (country wise).
snip<=-
Ok, so with a bit of work, I was able to generate a country report based on thenodelist. I'm not sure if you're using MakeNL for the nodelist segments or not,but perhaps you could take a look at Net 3 segment, and make sure the threeletter country code is at the end of the city/state section. I did manuallychange them in my test nodelist.
Here is a rough draft of the output at this point. It does need to be beautified a bit though. :)
Ok, so with a bit of work, I was able to generate a country report based on the nodelist. I'm not sure if you're using MakeNL for the nodelist segments or not, but perhaps you could take a look at Net 3 segment, and make sure the three letter
country code is at the end of the city/state section. I did manually change them in my test nodelist.
I do use makenl, but not sure that Avon takes my segment as received
(yet atleast)...
Are settling on ISO 2 char or 3 char country names? (I've always used 2, butsee that you have 3... :)
AUS **** 20 7.97%
NZL *** 12 4.78%
the nodelist. Before you ask, the 'XXX' was added to the listing you
have for 1/999.
This report is showing the last three characters of the city/state field of the nodelist, so we will need to double check to make sure they are
all set up in that format. When I originally ran it, I had a node in 'NLD', and another one in 'Netherlands'.
I'll keep you posted as to making it look better. :)
AUS **** 20 7.97
NZL *** 12 4.78
Darn beaten by the Aussies again - sigh :)
Also need to keep in mind, how many systems are actually processing a nodelist? I know that Mystic does, but it's more for sending to nodes that
Are settling on ISO 2 char or 3 char country names? (I've always used butsee that you have 3... :)
I've always used the 2 char, but Paul has been using 3, so I went with that instead of changing all of them. :)
the nodelist. Before you ask, the 'XXX' was added to the listing you have for 1/999.
Ahh..
My reference guide for using country codes in the fsxNet nodelist has beenthis web page https://en.wikipedia.org/wiki/ISO_3166-1#Current_codes
I use the Alpha 3 codes - hope that helps.
Your comment made me realise as we get closer to having regular segments being incorporated into the nodelist from HUBs it's important we are all using the same song sheet.
I'll keep you posted as to making it look better. :)
You're doing great :)
Want me to play with some numbers here? ;)
I've always used the 2 char, but Paul has been using 3, so I went wit that instead of changing all of them. :)
Yep 3 is the way please, it means I can decode by Bahamas from Bahrain :)
I do have the programs both set up on CRBBS. When a new nodelist comes
in, it*should* run them and post the messages into a local base here.
Once I knowit's working properly, being automated, I'll start posting
them into theFSX_STA echo.
On 24 Oct 2020 at 03:18a, Black Panther pondered and said...
It's in there. :)
Looks good.
I think if we us the U. in the nodelist, we could basically do
anything we want
Yep, but can we use U for one thing only?
| Sysop: | altere |
|---|---|
| Location: | Houston, TX |
| Users: | 60 |
| Nodes: | 4 (0 / 4) |
| Uptime: | 05:38:52 |
| Calls: | 516 |
| Files: | 7,012 |
| Messages: | 287,457 |