Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Allow user to specify log file name #727

Open
tonycanike opened this issue Oct 31, 2023 · 0 comments
Open

Allow user to specify log file name #727

tonycanike opened this issue Oct 31, 2023 · 0 comments

Comments

@tonycanike
Copy link
Contributor

Subject of the issue

Allow the user to specify the log file name to better organize their log data. There are industry standards for these file names, and SFE_FACET_yymmdd_hhmm.ubx does not comply with the industry standards. More importantly, when one is gathering data files from multiple receivers in a single session, it is very difficult to know which file is from which site/receiver.

The general industry solution to this problem is to allow the user to specify the filename of the log file. It is very common to have the first four characters of the filename be the name of the site (mark, survey point) the data was collected at.

I am referring to the log file that is variously referred to as the binary file, the ubx file, the raw file, or the proprietary log file.

When I get back to the office to process log files from four different Facets, it gets pretty confusing which log file is which.

There are a small number of RINEX file naming conventions designed to mitigate this issue. It's common among GNSS receiver manufacturers to allow the user to specify the binary log file name, and users often use a name for the binary file that is similar to the name they will use for the RINEX file, perhaps only varying in the .filetype

In the common RINEX filenaming standards, the first four characters of the file name are the name of the site (mark, monument, survey point) for which the log file was gathered. The rest of the filename usually specifies the datetime and other information about data gathering. Some post-processing software assumes that the first four characters of the filename are the name of the site.

If the user specifies an existing file name, that's on them, so I suggest appending to the existing file. Unless a more robust UI interaction is possible, or perhaps even appending an incrementing integer to the file name is possible.

If the user doesn't wish to specify a filename, revert to the existing filenaming technique (SFE_Facet_yymmdd_hhmm.ubx)

The user should be able to specify the filename via the WiFi config or the Serial config.

The specified filename shall be used for that logging session, and not for subsequent logging sessions. If the logging session terminates and a new one begins without the setting of a custom filename, revert to the existing filenaming technique.

I'm not sure how to define the end of a logging session and the beginning of a new one. I generally physically setup the Facet, power it on, go into WiFi config, get everything configured, click the "new log" button, exit/save/reboot, and walk away. I then come back 2-5 hours later and turn it off. If I power it back on, it's a different logging session. imagine others have more complicated use cases (mark, rebooting, power glitches, reconfiguring, etc.)

Your workbench

v3.10
Facet

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant