search

PrideLab / PRIDE-PPPAR

An open‑source software for Multi-GNSS PPP ambiguity resolution
http://pride.whu.edu.cn/
GNU General Public License v3.0
264 stars 103 forks source link

Bad lenght time computation with config Session Time with rinex 3 filenaming convention #6

Open aureliep972 opened 2 years ago

aureliep972 commented 2 years ago

Hi,

I'm using pdp3 to process rinex 3 files named after the rinex 3 convention. These files are 30H length centered around 12 PM of the day of study.

However, the config file created by pdp3 from the rinex 3 convention naming file computes the study length as of 97200.00 seconds, when it should be 107970.00 seconds. Then, the resulting kin file doesn't get the whole observations, and it actually gets the results for the day before from 21h to 23h59m30s, and the day of study from 21h to 23h59m30s also, with a gap of no results at all between these two intervals.

I solved the problem just by naming the rinex 3 file after the rinex 2 convention, which works really well, but there is still an issue with rinex 3 naming convention files.

PrideLab commented 2 years ago

Sorry for the delay in responding as we have been on vacation for the past few weeks. We failed to repeat this bug and cannot determine if it is related to the specific observation file. Can you help us to solve this problem with more details such as your input command, running log/screenshots, or observation files (if they are public)?

Hi,

I'm using pdp3 to process rinex 3 files named after the rinex 3 convention. These files are 30H length centered around 12 PM of the day of study.

However, the config file created by pdp3 from the rinex 3 convention naming file computes the study length as of 97200.00 seconds, when it should be 107970.00 seconds. Then, the resulting kin file doesn't get the whole observations, and it actually gets the results for the day before from 21h to 23h59m30s, and the day of study from 21h to 23h59m30s also, with a gap of no results at all between these two intervals.

I solved the problem just by naming the rinex 3 file after the rinex 2 convention, which works really well, but there is still an issue with rinex 3 naming convention files.

MateuszPiskorski commented 2 years ago

I've run test script only several times and it always fails to download orbit files. I don't know why.

czw., 4 sie 2022, 16:38 użytkownik PrideLab @.***> napisał:

Sorry for the delay in responding as we have been on vacation for the past few weeks. We failed to repeat this bug and cannot determine if it is related to the specific observation file. Can you help us to solve this problem with more details such as your input command, running log/screenshots, or observation files (if they are public)?

Hi,

I'm using pdp3 to process rinex 3 files named after the rinex 3 convention. These files are 30H length centered around 12 PM of the day of study.

However, the config file created by pdp3 from the rinex 3 convention naming file computes the study length as of 97200.00 seconds, when it should be 107970.00 seconds. Then, the resulting kin file doesn't get the whole observations, and it actually gets the results for the day before from 21h to 23h59m30s, and the day of study from 21h to 23h59m30s also, with a gap of no results at all between these two intervals.

I solved the problem just by naming the rinex 3 file after the rinex 2 convention, which works really well, but there is still an issue with rinex 3 naming convention files.

— Reply to this email directly, view it on GitHub https://github.com/PrideLab/PRIDE-PPPAR/issues/6#issuecomment-1205349784, or unsubscribe https://github.com/notifications/unsubscribe-auth/ALR3Q2VS232MTFPUB6VKQALVXPIYFANCNFSM54GZ2CEQ . You are receiving this because you are subscribed to this thread.Message ID: @.***>

Waley04 commented 2 years ago

@MateuszPiskorski, Are you working on Mac or Linux?

PrideLab commented 2 years ago

Jing, Could you help?

Best, Jianghui

On Aug 5, 2022, at 1:01 AM, MateuszPiskorski @.***> wrote:

I've run test script only several times and it always fails to download orbit files. I don't know why.

czw., 4 sie 2022, 16:38 użytkownik PrideLab @.***> napisał:

Sorry for the delay in responding as we have been on vacation for the past few weeks. We failed to repeat this bug and cannot determine if it is related to the specific observation file. Can you help us to solve this problem with more details such as your input command, running log/screenshots, or observation files (if they are public)?

Hi,

I'm using pdp3 to process rinex 3 files named after the rinex 3 convention. These files are 30H length centered around 12 PM of the day of study.

However, the config file created by pdp3 from the rinex 3 convention naming file computes the study length as of 97200.00 seconds, when it should be 107970.00 seconds. Then, the resulting kin file doesn't get the whole observations, and it actually gets the results for the day before from 21h to 23h59m30s, and the day of study from 21h to 23h59m30s also, with a gap of no results at all between these two intervals.

I solved the problem just by naming the rinex 3 file after the rinex 2 convention, which works really well, but there is still an issue with rinex 3 naming convention files.

— Reply to this email directly, view it on GitHub https://github.com/PrideLab/PRIDE-PPPAR/issues/6#issuecomment-1205349784, or unsubscribe https://github.com/notifications/unsubscribe-auth/ALR3Q2VS232MTFPUB6VKQALVXPIYFANCNFSM54GZ2CEQ . You are receiving this because you are subscribed to this thread.Message ID: @.***>

— Reply to this email directly, view it on GitHub https://github.com/PrideLab/PRIDE-PPPAR/issues/6#issuecomment-1205528731, or unsubscribe https://github.com/notifications/unsubscribe-auth/ALPCKGJ5FNTWYBTXRSUJRR3VXPZOHANCNFSM54GZ2CEQ. You are receiving this because you commented.

MateuszPiskorski commented 2 years ago

@Waley04 On linux, but now it works just fine.

Waley04 commented 2 years ago

@MateuszPiskorski,

That is good news.

aureliep972 commented 2 years ago

Aurélie PANETIER (STIC/REMS) a partagé des fichiers OneDrive Entreprise avec vous. Pour les afficher, cliquez sur les liens ci-dessous. https://enstabretagne-my.sharepoint.com/:u:/g/personal/aurelie_panetier_ensta-bretagne_org/EVLapT86dgVJvfK0U8qTjYgBhh6VRs2bWjceMDwggQfUCQ [https://r1.res.office365.com/owa/prem/images/dc-generic_20.png]https://enstabretagne-my.sharepoint.com/:u:/g/personal/aurelie_panetier_ensta-bretagne_org/EVLapT86dgVJvfK0U8qTjYgBhh6VRs2bWjceMDwggQfUCQ at2x202z.15ohttps://enstabretagne-my.sharepoint.com/:u:/g/personal/aurelie_panetier_ensta-bretagne_org/EVLapT86dgVJvfK0U8qTjYgBhh6VRs2bWjceMDwggQfUCQ

https://enstabretagne-my.sharepoint.com/:u:/g/personal/aurelie_panetier_ensta-bretagne_org/EYDOH1ONPTBHoBozEZypyqoBpGOceZ5QL-XuUtSQ-ZQFlw [https://r1.res.office365.com/owa/prem/images/dc-generic_20.png]https://enstabretagne-my.sharepoint.com/:u:/g/personal/aurelie_panetier_ensta-bretagne_org/EYDOH1ONPTBHoBozEZypyqoBpGOceZ5QL-XuUtSQ-ZQFlw at2x203z.15ohttps://enstabretagne-my.sharepoint.com/:u:/g/personal/aurelie_panetier_ensta-bretagne_org/EYDOH1ONPTBHoBozEZypyqoBpGOceZ5QL-XuUtSQ-ZQFlw

https://enstabretagne-my.sharepoint.com/:u:/g/personal/aurelie_panetier_ensta-bretagne_org/EY1BCM2D8JhIqVWGTrN1VBABtRF3PvfSOrAagVhXMD7zIw [https://r1.res.office365.com/owa/prem/images/dc-generic_20.png]https://enstabretagne-my.sharepoint.com/:u:/g/personal/aurelie_panetier_ensta-bretagne_org/EY1BCM2D8JhIqVWGTrN1VBABtRF3PvfSOrAagVhXMD7zIw AT2_00000_R_20152030000_01D_01S_GO.crxhttps://enstabretagne-my.sharepoint.com/:u:/g/personal/aurelie_panetier_ensta-bretagne_org/EY1BCM2D8JhIqVWGTrN1VBABtRF3PvfSOrAagVhXMD7zIw

https://enstabretagne-my.sharepoint.com/:u:/g/personal/aurelie_panetier_ensta-bretagne_org/EShlTNOEGjpEq2qzSd5YnFsBVYcNjM5jMa6AvXB60TFxDw [https://r1.res.office365.com/owa/prem/images/dc-generic_20.png]https://enstabretagne-my.sharepoint.com/:u:/g/personal/aurelie_panetier_ensta-bretagne_org/EShlTNOEGjpEq2qzSd5YnFsBVYcNjM5jMa6AvXB60TFxDw AT2_00000_R_20152020000_01D_01S_GO.crxhttps://enstabretagne-my.sharepoint.com/:u:/g/personal/aurelie_panetier_ensta-bretagne_org/EShlTNOEGjpEq2qzSd5YnFsBVYcNjM5jMa6AvXB60TFxDw

Thank you for trying to help me.

I am working on Linux.

You can find attached the files I processed. The Rinex3 style files are the original ones. The Rinex2 style filename files are the Rinex3 files renamed after the Rinex2 convention.

The problem here is that, when I execute: "pdp3 -m K -n AT2X at2x202z.15o" in my terminal, the resulting file contains the whole 30h of data (please see the attached file kin_2015201_at2x_RNX2). Then, this is fine. But when I process: "pdp3 -m K -n AT2X AT2X00000_R_20152020000_30H_30S_GO.rnx", the resulting file contains only the data between 21h and 23h59 of the day 201, and the data between 21h and 23h59 of the day 202 (please see the attached file kin_2015201_at2x_RNX3). The rest in not processed even if the processed file is exactly the same than before, but with a Rinex3 convention name instead of Rinex2.

Also, I attached two days of files because I cannot process correctly the files when I put the command line: "pdp3 -m K -s 2015/201 -e 2015/204 -n AT2X at2x202z.15o". Indeed, whether I put the Rinex2 or Rinex3 file name style, the processing results only in one kin file containing the results for the first day of study. I haven't tried it for a while, but I think I remember it worked with normal 24h files. Actually, it is less important than the problem before, because I just created a loop that launches the command lines on all my files, and for now I think this method is rapid enough for me to work this way (at the end I will need to process 7 years of data).

I hope it is clear enought.

Thanks again for your help.

Kind Regards,

[Logo ENSTA Bretagne]https://www.ensta-bretagne.fr [Logo LabSTIC] https://www.labsticc.fr/en/index/ [Logo MathStic] https://ed-mathstic.u-bretagneloire.fr/ Aurélie PANETIER STIC - REMS / PhD Student Ecole Doctorale MathSTIC - ED601 @.*** M114

ENSTA Bretagne Grande école d'ingénieurs et centre de recherche French State Graduate, Post-Graduate and Research Institute 2 rue François Verny - 29806 Brest Cedex 9 - France www.ensta-bretagne.frhttps://www.ensta-bretagne.fr

De : PrideLab @.> Envoyé : jeudi 4 août 2022 16:38 À : PrideLab/PRIDE-PPPAR @.> Cc : Aurélie PANETIER (STIC/REMS) @.>; Author @.> Objet : Re: [PrideLab/PRIDE-PPPAR] Bad lenght time computation with config Session Time with rinex 3 filenaming convention (Issue #6)

Sorry for the delay in responding as we have been on vacation for the past few weeks. We failed to repeat this bug and cannot determine if it is related to the specific observation file. Can you help us to solve this problem with more details such as your input command, running log/screenshots, or observation files (if they are public)?

Hi,

I'm using pdp3 to process rinex 3 files named after the rinex 3 convention. These files are 30H length centered around 12 PM of the day of study.

However, the config file created by pdp3 from the rinex 3 convention naming file computes the study length as of 97200.00 seconds, when it should be 107970.00 seconds. Then, the resulting kin file doesn't get the whole observations, and it actually gets the results for the day before from 21h to 23h59m30s, and the day of study from 21h to 23h59m30s also, with a gap of no results at all between these two intervals.

I solved the problem just by naming the rinex 3 file after the rinex 2 convention, which works really well, but there is still an issue with rinex 3 naming convention files.

— Reply to this email directly, view it on GitHubhttps://github.com/PrideLab/PRIDE-PPPAR/issues/6#issuecomment-1205349784, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AS2OLFIDBHYD4BRMMB3CKV3VXPIYDANCNFSM54GZ2CEQ. You are receiving this because you authored the thread.Message ID: @.***>

ZJksc commented 2 years ago

Aurélie PANETIER (STIC/REMS) a partagé des fichiers OneDrive Entreprise avec vous. Pour les afficher, cliquez sur les liens ci-dessous. https://enstabretagne-my.sharepoint.com/:u:/g/personal/aurelie_panetier_ensta-bretagne_org/EVLapT86dgVJvfK0U8qTjYgBhh6VRs2bWjceMDwggQfUCQ [https://r1.res.office365.com/owa/prem/images/dc-generic_20.png]<https://enstabretagne-my.sharepoint.com/:u:/g/personal/aurelie_panetier_ensta-bretagne_org/EVLapT86dgVJvfK0U8qTjYgBhh6VRs2bWjceMDwggQfUCQ> at2x202z.15ohttps://enstabretagne-my.sharepoint.com/:u:/g/personal/aurelie_panetier_ensta-bretagne_org/EVLapT86dgVJvfK0U8qTjYgBhh6VRs2bWjceMDwggQfUCQ https://enstabretagne-my.sharepoint.com/:u:/g/personal/aurelie_panetier_ensta-bretagne_org/EYDOH1ONPTBHoBozEZypyqoBpGOceZ5QL-XuUtSQ-ZQFlw [https://r1.res.office365.com/owa/prem/images/dc-generic_20.png]<https://enstabretagne-my.sharepoint.com/:u:/g/personal/aurelie_panetier_ensta-bretagne_org/EYDOH1ONPTBHoBozEZypyqoBpGOceZ5QL-XuUtSQ-ZQFlw> at2x203z.15ohttps://enstabretagne-my.sharepoint.com/:u:/g/personal/aurelie_panetier_ensta-bretagne_org/EYDOH1ONPTBHoBozEZypyqoBpGOceZ5QL-XuUtSQ-ZQFlw https://enstabretagne-my.sharepoint.com/:u:/g/personal/aurelie_panetier_ensta-bretagne_org/EY1BCM2D8JhIqVWGTrN1VBABtRF3PvfSOrAagVhXMD7zIw [https://r1.res.office365.com/owa/prem/images/dc-generic_20.png]<https://enstabretagne-my.sharepoint.com/:u:/g/personal/aurelie_panetier_ensta-bretagne_org/EY1BCM2D8JhIqVWGTrN1VBABtRF3PvfSOrAagVhXMD7zIw> AT2_00000_R_20152030000_01D_01S_GO.crxhttps://enstabretagne-my.sharepoint.com/:u:/g/personal/aurelie_panetier_ensta-bretagne_org/EY1BCM2D8JhIqVWGTrN1VBABtRF3PvfSOrAagVhXMD7zIw https://enstabretagne-my.sharepoint.com/:u:/g/personal/aurelie_panetier_ensta-bretagne_org/EShlTNOEGjpEq2qzSd5YnFsBVYcNjM5jMa6AvXB60TFxDw [https://r1.res.office365.com/owa/prem/images/dc-generic_20.png]<https://enstabretagne-my.sharepoint.com/:u:/g/personal/aurelie_panetier_ensta-bretagne_org/EShlTNOEGjpEq2qzSd5YnFsBVYcNjM5jMa6AvXB60TFxDw> AT2_00000_R_20152020000_01D_01S_GO.crxhttps://enstabretagne-my.sharepoint.com/:u:/g/personal/aurelie_panetier_ensta-bretagne_org/EShlTNOEGjpEq2qzSd5YnFsBVYcNjM5jMa6AvXB60TFxDw Thank you for trying to help me. I am working on Linux. You can find attached the files I processed. The Rinex3 style files are the original ones. The Rinex2 style filename files are the Rinex3 files renamed after the Rinex2 convention. The problem here is that, when I execute: "pdp3 -m K -n AT2X at2x202z.15o" in my terminal, the resulting file contains the whole 30h of data (please see the attached file kin_2015201_at2x_RNX2). Then, this is fine. But when I process: "pdp3 -m K -n AT2X AT2X00000_R_20152020000_30H_30S_GO.rnx", the resulting file contains only the data between 21h and 23h59 of the day 201, and the data between 21h and 23h59 of the day 202 (please see the attached file kin_2015201_at2x_RNX3). The rest in not processed even if the processed file is exactly the same than before, but with a Rinex3 convention name instead of Rinex2. Also, I attached two days of files because I cannot process correctly the files when I put the command line: "pdp3 -m K -s 2015/201 -e 2015/204 -n AT2X at2x202z.15o". Indeed, whether I put the Rinex2 or Rinex3 file name style, the processing results only in one kin file containing the results for the first day of study. I haven't tried it for a while, but I think I remember it worked with normal 24h files. Actually, it is less important than the problem before, because I just created a loop that launches the command lines on all my files, and for now I think this method is rapid enough for me to work this way (at the end I will need to process 7 years of data). I hope it is clear enought. Thanks again for your help. Kind Regards, [Logo ENSTA Bretagne]https://www.ensta-bretagne.fr [Logo LabSTIC] https://www.labsticc.fr/en/index/ [Logo MathStic] https://ed-mathstic.u-bretagneloire.fr/ Aurélie PANETIER STIC - REMS / PhD Student Ecole Doctorale MathSTIC - ED601 @. M114 ENSTA Bretagne Grande école d'ingénieurs et centre de recherche French State Graduate, Post-Graduate and Research Institute 2 rue François Verny - 29806 Brest Cedex 9 - France www.ensta-bretagne.fr<https://www.ensta-bretagne.fr> … ____ De : PrideLab @.> Envoyé : jeudi 4 août 2022 16:38 À : PrideLab/PRIDE-PPPAR @.> Cc : Aurélie PANETIER (STIC/REMS) @.>; Author @.> Objet : Re: [PrideLab/PRIDE-PPPAR] Bad lenght time computation with config Session Time with rinex 3 filenaming convention (Issue #6) Sorry for the delay in responding as we have been on vacation for the past few weeks. We failed to repeat this bug and cannot determine if it is related to the specific observation file. Can you help us to solve this problem with more details such as your input command, running log/screenshots, or observation files (if they are public)? Hi, I'm using pdp3 to process rinex 3 files named after the rinex 3 convention. These files are 30H length centered around 12 PM of the day of study. However, the config file created by pdp3 from the rinex 3 convention naming file computes the study length as of 97200.00 seconds, when it should be 107970.00 seconds. Then, the resulting kin file doesn't get the whole observations, and it actually gets the results for the day before from 21h to 23h59m30s, and the day of study from 21h to 23h59m30s also, with a gap of no results at all between these two intervals. I solved the problem just by naming the rinex 3 file after the rinex 2 convention, which works really well, but there is still an issue with rinex 3 naming convention files. — Reply to this email directly, view it on GitHub<#6 (comment)>, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AS2OLFIDBHYD4BRMMB3CKV3VXPIYDANCNFSM54GZ2CEQ. You are receiving this because you authored the thread.Message ID: @.>

Hi,

The Rinex3 observation file used in your proposed issue is AT2X00000_R_20152020000_30H_30S_GO.rnx, But the attachment you sent is AT2_00000_R_20152020000_01D_01S_GO.crx, which only has single-day observations. Are these two files the same?

I tried to rename the attached Rinex 2 file to the Rinex 3 file name you are using, and the length is normal.

$ cp at2x202z.15o AT2X00000_R_20152020000_30H_30S_GO.rnx

$ pdp3 -m K -n AT2X data/AT2X00000_R_20152020000_30H_30S_GO.rnx

Did you send the wrong file, or the original file is not the same?

Best regard,

time_len

aureliep972 commented 2 years ago

Aurélie PANETIER (STIC/REMS) a partagé des fichiers OneDrive Entreprise avec vous. Pour les afficher, cliquez sur les liens ci-dessous. https://enstabretagne-my.sharepoint.com/:u:/g/personal/aurelie_panetier_ensta-bretagne_org/EbcW6sQcmnlCq39H0Dj2lZYBb_8bjn20wM4hCaeVZfDOxQ [https://r1.res.office365.com/owa/prem/images/dc-generic_20.png]https://enstabretagne-my.sharepoint.com/:u:/g/personal/aurelie_panetier_ensta-bretagne_org/EbcW6sQcmnlCq39H0Dj2lZYBb_8bjn20wM4hCaeVZfDOxQ AT2X00000_R_20152020000_30H_30S_GO.rnxhttps://enstabretagne-my.sharepoint.com/:u:/g/personal/aurelie_panetier_ensta-bretagne_org/EbcW6sQcmnlCq39H0Dj2lZYBb_8bjn20wM4hCaeVZfDOxQ

https://enstabretagne-my.sharepoint.com/:u:/g/personal/aurelie_panetier_ensta-bretagne_org/EVrAlNKExGxDvCcN4CugHa4BPRkzKWWQMRl61u2-7wVQ-w [https://r1.res.office365.com/owa/prem/images/dc-generic_20.png]https://enstabretagne-my.sharepoint.com/:u:/g/personal/aurelie_panetier_ensta-bretagne_org/EVrAlNKExGxDvCcN4CugHa4BPRkzKWWQMRl61u2-7wVQ-w AT2X00000_R_20152030000_30H_30S_GO.rnxhttps://enstabretagne-my.sharepoint.com/:u:/g/personal/aurelie_panetier_ensta-bretagne_org/EVrAlNKExGxDvCcN4CugHa4BPRkzKWWQMRl61u2-7wVQ-w

Indeed you're right, I mismatched the files. Sorry. Here are the Rinex 3 files I'm processing with Pride PPP AR.

[Logo ENSTA Bretagne]https://www.ensta-bretagne.fr [Logo LabSTIC] https://www.labsticc.fr/en/index/ [Logo MathStic] https://ed-mathstic.u-bretagneloire.fr/ Aurélie PANETIER STIC - REMS / PhD Student Ecole Doctorale MathSTIC - ED601 @.*** M114

ENSTA Bretagne Grande école d'ingénieurs et centre de recherche French State Graduate, Post-Graduate and Research Institute 2 rue François Verny - 29806 Brest Cedex 9 - France www.ensta-bretagne.frhttps://www.ensta-bretagne.fr

De : ZJksc @.> Envoyé : mardi 6 septembre 2022 05:33 À : PrideLab/PRIDE-PPPAR @.> Cc : Aurélie PANETIER (STIC/REMS) @.>; Author @.> Objet : Re: [PrideLab/PRIDE-PPPAR] Bad lenght time computation with config Session Time with rinex 3 filenaming convention (Issue #6)

Aurélie PANETIER (STIC/REMS) a partagé des fichiers OneDrive Entreprise avec vous. Pour les afficher, cliquez sur les liens ci-dessous. https://enstabretagne-my.sharepoint.com/:u:/g/personal/aurelie_panetier_ensta-bretagne_org/EVLapT86dgVJvfK0U8qTjYgBhh6VRs2bWjceMDwggQfUCQ [https://r1.res.office365.com/owa/prem/images/dc-generic_20.png]https://enstabretagne-my.sharepoint.com/:u:/g/personal/aurelie_panetier_ensta-bretagne_org/EVLapT86dgVJvfK0U8qTjYgBhh6VRs2bWjceMDwggQfUCQ<https://r1.res.office365.com/owa/prem/images/dc-generic_20.png%5D%3Chttps://enstabretagne-my.sharepoint.com/:u:/g/personal/aurelie_panetier_ensta-bretagne_org/EVLapT86dgVJvfK0U8qTjYgBhh6VRs2bWjceMDwggQfUCQ> at2x202z.15ohttps://enstabretagne-my.sharepoint.com/:u:/g/personal/aurelie_panetier_ensta-bretagne_org/EVLapT86dgVJvfK0U8qTjYgBhh6VRs2bWjceMDwggQfUCQ https://enstabretagne-my.sharepoint.com/:u:/g/personal/aurelie_panetier_ensta-bretagne_org/EYDOH1ONPTBHoBozEZypyqoBpGOceZ5QL-XuUtSQ-ZQFlw [https://r1.res.office365.com/owa/prem/images/dc-generic_20.png]https://enstabretagne-my.sharepoint.com/:u:/g/personal/aurelie_panetier_ensta-bretagne_org/EYDOH1ONPTBHoBozEZypyqoBpGOceZ5QL-XuUtSQ-ZQFlw<https://r1.res.office365.com/owa/prem/images/dc-generic_20.png%5D%3Chttps://enstabretagne-my.sharepoint.com/:u:/g/personal/aurelie_panetier_ensta-bretagne_org/EYDOH1ONPTBHoBozEZypyqoBpGOceZ5QL-XuUtSQ-ZQFlw> at2x203z.15ohttps://enstabretagne-my.sharepoint.com/:u:/g/personal/aurelie_panetier_ensta-bretagne_org/EYDOH1ONPTBHoBozEZypyqoBpGOceZ5QL-XuUtSQ-ZQFlw https://enstabretagne-my.sharepoint.com/:u:/g/personal/aurelie_panetier_ensta-bretagne_org/EY1BCM2D8JhIqVWGTrN1VBABtRF3PvfSOrAagVhXMD7zIw [https://r1.res.office365.com/owa/prem/images/dc-generic_20.png]https://enstabretagne-my.sharepoint.com/:u:/g/personal/aurelie_panetier_ensta-bretagne_org/EY1BCM2D8JhIqVWGTrN1VBABtRF3PvfSOrAagVhXMD7zIw<https://r1.res.office365.com/owa/prem/images/dc-generic_20.png%5D%3Chttps://enstabretagne-my.sharepoint.com/:u:/g/personal/aurelie_panetier_ensta-bretagne_org/EY1BCM2D8JhIqVWGTrN1VBABtRF3PvfSOrAagVhXMD7zIw> AT2_00000_R_20152030000_01D_01S_GO.crxhttps://enstabretagne-my.sharepoint.com/:u:/g/personal/aurelie_panetier_ensta-bretagne_org/EY1BCM2D8JhIqVWGTrN1VBABtRF3PvfSOrAagVhXMD7zIw https://enstabretagne-my.sharepoint.com/:u:/g/personal/aurelie_panetier_ensta-bretagne_org/EShlTNOEGjpEq2qzSd5YnFsBVYcNjM5jMa6AvXB60TFxDw [https://r1.res.office365.com/owa/prem/images/dc-generic_20.png]https://enstabretagne-my.sharepoint.com/:u:/g/personal/aurelie_panetier_ensta-bretagne_org/EShlTNOEGjpEq2qzSd5YnFsBVYcNjM5jMa6AvXB60TFxDw<https://r1.res.office365.com/owa/prem/images/dc-generic_20.png%5D%3Chttps://enstabretagne-my.sharepoint.com/:u:/g/personal/aurelie_panetier_ensta-bretagne_org/EShlTNOEGjpEq2qzSd5YnFsBVYcNjM5jMa6AvXB60TFxDw> AT2_00000_R_20152020000_01D_01S_GO.crxhttps://enstabretagne-my.sharepoint.com/:u:/g/personal/aurelie_panetier_ensta-bretagne_org/EShlTNOEGjpEq2qzSd5YnFsBVYcNjM5jMa6AvXB60TFxDw Thank you for trying to help me. I am working on Linux. You can find attached the files I processed. The Rinex3 style files are the original ones. The Rinex2 style filename files are the Rinex3 files renamed after the Rinex2 convention. The problem here is that, when I execute: "pdp3 -m K -n AT2X at2x202z.15o" in my terminal, the resulting file contains the whole 30h of data (please see the attached file kin_2015201_at2x_RNX2). Then, this is fine. But when I process: "pdp3 -m K -n AT2X AT2X00000_R_20152020000_30H_30S_GO.rnx", the resulting file contains only the data between 21h and 23h59 of the day 201, and the data between 21h and 23h59 of the day 202 (please see the attached file kin_2015201_at2x_RNX3). The rest in not processed even if the processed file is exactly the same than before, but with a Rinex3 convention name instead of Rinex2. Also, I attached two days of files because I cannot process correctly the files when I put the command line: "pdp3 -m K -s 2015/201 -e 2015/204 -n AT2X at2x202z.15o". Indeed, whether I put the Rinex2 or Rinex3 file name style, the processing results only in one kin file containing the results for the first day of study. I haven't tried it for a while, but I think I remember it worked with normal 24h files. Actually, it is less important than the problem before, because I just created a loop that launches the command lines on all my files, and for now I think this method is rapid enough for me to work this way (at the end I will need to process 7 years of data). I hope it is clear enought. Thanks again for your help. Kind Regards, [Logo ENSTA Bretagne]https://www.ensta-bretagne.fr [Logo LabSTIC] https://www.labsticc.fr/en/index/ [Logo MathStic] https://ed-mathstic.u-bretagneloire.fr/ Aurélie PANETIER STIC - REMS / PhD Student Ecole Doctorale MathSTIC - ED601 @. M114 ENSTA Bretagne Grande école d'ingénieurs et centre de recherche French State Graduate, Post-Graduate and Research Institute 2 rue François Verny - 29806 Brest Cedex 9 - France www.ensta-bretagne.frhttps://www.ensta-bretagne.fr<http://www.ensta-bretagne.fr%3Chttps://www.ensta-bretagne.fr> … ____ De : PrideLab @.> Envoyé : jeudi 4 août 2022 16:38 À : PrideLab/PRIDE-PPPAR @.> Cc : Aurélie PANETIER (STIC/REMS) @.>; Author @.> Objet : Re: [PrideLab/PRIDE-PPPAR] Bad lenght time computation with config Session Time with rinex 3 filenaming convention (Issue #6https://github.com/PrideLab/PRIDE-PPPAR/issues/6) Sorry for the delay in responding as we have been on vacation for the past few weeks. We failed to repeat this bug and cannot determine if it is related to the specific observation file. Can you help us to solve this problem with more details such as your input command, running log/screenshots, or observation files (if they are public)? Hi, I'm using pdp3 to process rinex 3 files named after the rinex 3 convention. These files are 30H length centered around 12 PM of the day of study. However, the config file created by pdp3 from the rinex 3 convention naming file computes the study length as of 97200.00 seconds, when it should be 107970.00 seconds. Then, the resulting kin file doesn't get the whole observations, and it actually gets the results for the day before from 21h to 23h59m30s, and the day of study from 21h to 23h59m30s also, with a gap of no results at all between these two intervals. I solved the problem just by naming the rinex 3 file after the rinex 2 convention, which works really well, but there is still an issue with rinex 3 naming convention files. — Reply to this email directly, view it on GitHub<#6 (comment)https://github.com/PrideLab/PRIDE-PPPAR/issues/6#issuecomment-1205349784>, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AS2OLFIDBHYD4BRMMB3CKV3VXPIYDANCNFSM54GZ2CEQ. You are receiving this because you authored the thread.Message ID: @.>

Hi,

The Rinex3 observation file used in your proposed issue is AT2X00000_R_20152020000_30H_30S_GO.rnx, But the attachment you sent is AT2_00000_R_20152020000_01D_01S_GO.crx, which only has single-day observations. Are these two files the same?

I tried to rename the attached Rinex 2 file to the Rinex 3 file name you are using, and the length is normal.

$ cp at2x202z.15o AT2X00000_R_20152020000_30H_30S_GO.rnx

$ pdp3 -m K -n AT2X data/AT2X00000_R_20152020000_30H_30S_GO.rnx

Did you send the wrong file, or the original file is not the same?

Best regard,

[time_len]https://user-images.githubusercontent.com/84887830/188541460-01d84d26-00c6-4ab1-8a2b-7463e50a4457.png

— Reply to this email directly, view it on GitHubhttps://github.com/PrideLab/PRIDE-PPPAR/issues/6#issuecomment-1237621170, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AS2OLFIFPN4GOVKRLALJK6LV423Q5ANCNFSM54GZ2CEQ. You are receiving this because you authored the thread.Message ID: @.***>