Skip to content

Unexpected solu. quality degradation after adding '2L' frequency to config_f9p.py #11

@liusheng2020

Description

@liusheng2020

First of all, I would like to express my sincere gratitude for your excellent work. Your contributions have been incredibly helpful.

I ran the example data without any issues. When I switched to my own F9P data, it also worked fine (I made a minor modification because my base observations had 2W and 2X in the second frequency band, which would cause an error if not modified; the modification should not affect the program's solution). The minor modification is as follows :

Image

The solution results are as follows (you can see that among the 1102 results, Q=1 accounts for 95.8%):

Image

The above results were obtained using the unmodified src/config_f9p.py file from the repository.

However, when I added '2L': rSIG.L2L to the sig_tbl variable in the src/config_f9p.py file (considering that my rover observation file contains the 2L frequency band), the solution results all dropped to Q=2. As shown in the following image:

Image

Image

I am not sure why this happened. I have attached my data files below for your reference.

Thank you again for your time and effort. I look forward to your insights.

Best regards

Image

myUbloxF9Pdata.zip

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions