Trimble Business Center

Hi,
I have processed the baseline for GNSS observations, the results of the baseline process have been fixed but there is a red mark for the vertical point tolerance. What do these red flags mean and how can I solve this problem?
This is the Point Derivation Report
Thanks


------------------------------
Naufal Dwiakram
------------------------------

That has been discussed just a few days ago.
https://community.trimble.com/communities/community-homepage/digestviewer/viewquestion?ContributedContentKey=1ae7ef14-9992-45de-a287-c97ea4d3dfea&CommunityKey=d961b046-1661-40f3-8d7e-0bde6866a14d

Quoting Scot Roberts:
"A lot of times it's due to coordinates in the job file(s) from before the data was processed and they simply need to be removed or disabled so the observations can take over."

And that seems exactly what your point derivation report shows. Are you positive that your project is correctly setup, correct coordinate system and geoid?
If that is the case and you still see this error you'll have to disable the global coordinate that came with the static survey file, and re-compute the project (F4).
The resulting coordinates shouldn't change, since the observations should have taken precedence over the arbitrary coordinate from the static file. TBC just shows you that there is a large discrepancy between this coordinate and the one derived from base line processing and adjustment. Question is why it is that large? Hence my question about the correct project setup.


------------------------------
Ronny Schneider
------------------------------

Original Message:
Sent: 05-08-2022 19:54
From: Naufal Dwiakram
Subject: Point Out of Tolerance GNSS Processing

Hi,
I have processed the baseline for GNSS observations, the results of the baseline process have been fixed but there is a red mark for the vertical point tolerance. What do these red flags mean and how can I solve this problem?
This is the Point Derivation Report
Thanks


------------------------------
Naufal Dwiakram
------------------------------

I'm sure that the coordinate system is correct. It work the red flag went away when I disable the global files, but I'm still confused about this issue. Does this happen because of the out-of-tolerance difference in vertical point coordinates between the original file from rinex and the baseline computation?

------------------------------
Naufal Dwiakram
------------------------------

Original Message:
Sent: 05-08-2022 22:02
From: Ronny Schneider
Subject: Point Out of Tolerance GNSS Processing

That has been discussed just a few days ago.
https://community.trimble.com/communities/community-homepage/digestviewer/viewquestion?ContributedContentKey=1ae7ef14-9992-45de-a287-c97ea4d3dfea&CommunityKey=d961b046-1661-40f3-8d7e-0bde6866a14d

Quoting Scot Roberts:
"A lot of times it's due to coordinates in the job file(s) from before the data was processed and they simply need to be removed or disabled so the observations can take over."

And that seems exactly what your point derivation report shows. Are you positive that your project is correctly setup, correct coordinate system and geoid?
If that is the case and you still see this error you'll have to disable the global coordinate that came with the static survey file, and re-compute the project (F4).
The resulting coordinates shouldn't change, since the observations should have taken precedence over the arbitrary coordinate from the static file. TBC just shows you that there is a large discrepancy between this coordinate and the one derived from base line processing and adjustment. Question is why it is that large? Hence my question about the correct project setup.


------------------------------
Ronny Schneider

Original Message:
Sent: 05-08-2022 19:54
From: Naufal Dwiakram
Subject: Point Out of Tolerance GNSS Processing

Hi,
I have processed the baseline for GNSS observations, the results of the baseline process have been fixed but there is a red mark for the vertical point tolerance. What do these red flags mean and how can I solve this problem?
This is the Point Derivation Report
Thanks


------------------------------
Naufal Dwiakram
------------------------------

I'm not sure how the coordinate is computed that is stored inside static file. But it seems that those coordinates deviate in your case by 25 m or so in elevation from the adjusted coordinates when fixed to some control marks.
I actually haven't seen this issue with my static files yet. My deviations are around 1-2 m.

------------------------------
Ronny Schneider
------------------------------

Original Message:
Sent: 05-09-2022 00:07
From: Naufal Dwiakram
Subject: Point Out of Tolerance GNSS Processing

I'm sure that the coordinate system is correct. It work the red flag went away when I disable the global files, but I'm still confused about this issue. Does this happen because of the out-of-tolerance difference in vertical point coordinates between the original file from rinex and the baseline computation?

------------------------------
Naufal Dwiakram

Original Message:
Sent: 05-08-2022 22:02
From: Ronny Schneider
Subject: Point Out of Tolerance GNSS Processing

That has been discussed just a few days ago.
https://community.trimble.com/communities/community-homepage/digestviewer/viewquestion?ContributedContentKey=1ae7ef14-9992-45de-a287-c97ea4d3dfea&CommunityKey=d961b046-1661-40f3-8d7e-0bde6866a14d

Quoting Scot Roberts:
"A lot of times it's due to coordinates in the job file(s) from before the data was processed and they simply need to be removed or disabled so the observations can take over."

And that seems exactly what your point derivation report shows. Are you positive that your project is correctly setup, correct coordinate system and geoid?
If that is the case and you still see this error you'll have to disable the global coordinate that came with the static survey file, and re-compute the project (F4).
The resulting coordinates shouldn't change, since the observations should have taken precedence over the arbitrary coordinate from the static file. TBC just shows you that there is a large discrepancy between this coordinate and the one derived from base line processing and adjustment. Question is why it is that large? Hence my question about the correct project setup.


------------------------------
Ronny Schneider

Original Message:
Sent: 05-08-2022 19:54
From: Naufal Dwiakram
Subject: Point Out of Tolerance GNSS Processing

Hi,
I have processed the baseline for GNSS observations, the results of the baseline process have been fixed but there is a red mark for the vertical point tolerance. What do these red flags mean and how can I solve this problem?
This is the Point Derivation Report
Thanks


------------------------------
Naufal Dwiakram
------------------------------

Yes, the red flags appear because the point/coordinate "out-of-tolerance" in your settings is surpassed. If you went and changed those settings the flags would go away, but I don't recommend that. The original Global file you have there is a low accuracy point or unknown, was it a "here" start of the static file? I have had similar derivation reports, but usually all three are out and not just the vertical. In any case the GPS vectors seem to be working well with each other, so that leaves the first step to look at that Global coordinate, did something get entered incorrectly?

------------------------------
Sean Lahann, PLS
Phoenix, Arizona
------------------------------

Original Message:
Sent: 05-09-2022 00:07
From: Naufal Dwiakram
Subject: Point Out of Tolerance GNSS Processing

I'm sure that the coordinate system is correct. It work the red flag went away when I disable the global files, but I'm still confused about this issue. Does this happen because of the out-of-tolerance difference in vertical point coordinates between the original file from rinex and the baseline computation?

------------------------------
Naufal Dwiakram

Original Message:
Sent: 05-08-2022 22:02
From: Ronny Schneider
Subject: Point Out of Tolerance GNSS Processing

That has been discussed just a few days ago.
https://community.trimble.com/communities/community-homepage/digestviewer/viewquestion?ContributedContentKey=1ae7ef14-9992-45de-a287-c97ea4d3dfea&CommunityKey=d961b046-1661-40f3-8d7e-0bde6866a14d

Quoting Scot Roberts:
"A lot of times it's due to coordinates in the job file(s) from before the data was processed and they simply need to be removed or disabled so the observations can take over."

And that seems exactly what your point derivation report shows. Are you positive that your project is correctly setup, correct coordinate system and geoid?
If that is the case and you still see this error you'll have to disable the global coordinate that came with the static survey file, and re-compute the project (F4).
The resulting coordinates shouldn't change, since the observations should have taken precedence over the arbitrary coordinate from the static file. TBC just shows you that there is a large discrepancy between this coordinate and the one derived from base line processing and adjustment. Question is why it is that large? Hence my question about the correct project setup.


------------------------------
Ronny Schneider

Original Message:
Sent: 05-08-2022 19:54
From: Naufal Dwiakram
Subject: Point Out of Tolerance GNSS Processing

Hi,
I have processed the baseline for GNSS observations, the results of the baseline process have been fixed but there is a red mark for the vertical point tolerance. What do these red flags mean and how can I solve this problem?
This is the Point Derivation Report
Thanks


------------------------------
Naufal Dwiakram
------------------------------

I don't know where I missed or entered the data incorrectly, but I did the same step on other data, and the data looks fine. Does this indicate that the observation data is poor and should be re-observed?

------------------------------
Naufal Dwiakram
------------------------------

Original Message:
Sent: 05-09-2022 08:47
From: Sean Lahann
Subject: Point Out of Tolerance GNSS Processing

Yes, the red flags appear because the point/coordinate "out-of-tolerance" in your settings is surpassed. If you went and changed those settings the flags would go away, but I don't recommend that. The original Global file you have there is a low accuracy point or unknown, was it a "here" start of the static file? I have had similar derivation reports, but usually all three are out and not just the vertical. In any case the GPS vectors seem to be working well with each other, so that leaves the first step to look at that Global coordinate, did something get entered incorrectly?

------------------------------
Sean Lahann, PLS
Phoenix, Arizona

Original Message:
Sent: 05-09-2022 00:07
From: Naufal Dwiakram
Subject: Point Out of Tolerance GNSS Processing

I'm sure that the coordinate system is correct. It work the red flag went away when I disable the global files, but I'm still confused about this issue. Does this happen because of the out-of-tolerance difference in vertical point coordinates between the original file from rinex and the baseline computation?

------------------------------
Naufal Dwiakram

Original Message:
Sent: 05-08-2022 22:02
From: Ronny Schneider
Subject: Point Out of Tolerance GNSS Processing

That has been discussed just a few days ago.
https://community.trimble.com/communities/community-homepage/digestviewer/viewquestion?ContributedContentKey=1ae7ef14-9992-45de-a287-c97ea4d3dfea&CommunityKey=d961b046-1661-40f3-8d7e-0bde6866a14d

Quoting Scot Roberts:
"A lot of times it's due to coordinates in the job file(s) from before the data was processed and they simply need to be removed or disabled so the observations can take over."

And that seems exactly what your point derivation report shows. Are you positive that your project is correctly setup, correct coordinate system and geoid?
If that is the case and you still see this error you'll have to disable the global coordinate that came with the static survey file, and re-compute the project (F4).
The resulting coordinates shouldn't change, since the observations should have taken precedence over the arbitrary coordinate from the static file. TBC just shows you that there is a large discrepancy between this coordinate and the one derived from base line processing and adjustment. Question is why it is that large? Hence my question about the correct project setup.


------------------------------
Ronny Schneider

Original Message:
Sent: 05-08-2022 19:54
From: Naufal Dwiakram
Subject: Point Out of Tolerance GNSS Processing

Hi,
I have processed the baseline for GNSS observations, the results of the baseline process have been fixed but there is a red mark for the vertical point tolerance. What do these red flags mean and how can I solve this problem?
This is the Point Derivation Report
Thanks


------------------------------
Naufal Dwiakram
------------------------------

From what I can see in your report, the GPS observations have a higher quality rating than the control point coordinates for those same observed points, in all of the points. In other words the GPS vector solution produced a different coordinate (vertically) than the given coordinate. Without knowing exactly what you did and the other files associated to your project it is a little hard to make a call on what is the issue exactly. Your base could have the issue or possibly all your control coordinates are of low quality in the vertical. 

How was this survey done? Was it all static/rapid-static on known control points or unknowns. Did you start out with a control point file that you went and observed?

------------------------------
Sean Lahann, PLS
Phoenix, Arizona
------------------------------

Original Message:
Sent: 05-09-2022 19:47
From: Naufal Dwiakram
Subject: Point Out of Tolerance GNSS Processing

I don't know where I missed or entered the data incorrectly, but I did the same step on other data, and the data looks fine. Does this indicate that the observation data is poor and should be re-observed?

------------------------------
Naufal Dwiakram

Original Message:
Sent: 05-09-2022 08:47
From: Sean Lahann
Subject: Point Out of Tolerance GNSS Processing

Yes, the red flags appear because the point/coordinate "out-of-tolerance" in your settings is surpassed. If you went and changed those settings the flags would go away, but I don't recommend that. The original Global file you have there is a low accuracy point or unknown, was it a "here" start of the static file? I have had similar derivation reports, but usually all three are out and not just the vertical. In any case the GPS vectors seem to be working well with each other, so that leaves the first step to look at that Global coordinate, did something get entered incorrectly?

------------------------------
Sean Lahann, PLS
Phoenix, Arizona

Original Message:
Sent: 05-09-2022 00:07
From: Naufal Dwiakram
Subject: Point Out of Tolerance GNSS Processing

I'm sure that the coordinate system is correct. It work the red flag went away when I disable the global files, but I'm still confused about this issue. Does this happen because of the out-of-tolerance difference in vertical point coordinates between the original file from rinex and the baseline computation?

------------------------------
Naufal Dwiakram

Original Message:
Sent: 05-08-2022 22:02
From: Ronny Schneider
Subject: Point Out of Tolerance GNSS Processing

That has been discussed just a few days ago.
https://community.trimble.com/communities/community-homepage/digestviewer/viewquestion?ContributedContentKey=1ae7ef14-9992-45de-a287-c97ea4d3dfea&CommunityKey=d961b046-1661-40f3-8d7e-0bde6866a14d

Quoting Scot Roberts:
"A lot of times it's due to coordinates in the job file(s) from before the data was processed and they simply need to be removed or disabled so the observations can take over."

And that seems exactly what your point derivation report shows. Are you positive that your project is correctly setup, correct coordinate system and geoid?
If that is the case and you still see this error you'll have to disable the global coordinate that came with the static survey file, and re-compute the project (F4).
The resulting coordinates shouldn't change, since the observations should have taken precedence over the arbitrary coordinate from the static file. TBC just shows you that there is a large discrepancy between this coordinate and the one derived from base line processing and adjustment. Question is why it is that large? Hence my question about the correct project setup.


------------------------------
Ronny Schneider

Original Message:
Sent: 05-08-2022 19:54
From: Naufal Dwiakram
Subject: Point Out of Tolerance GNSS Processing

Hi,
I have processed the baseline for GNSS observations, the results of the baseline process have been fixed but there is a red mark for the vertical point tolerance. What do these red flags mean and how can I solve this problem?
This is the Point Derivation Report
Thanks


------------------------------
Naufal Dwiakram
------------------------------

I did this survey for GCP measurement using rapid static method with 15 minutes observation. The control point using benchmark point that already known the coordinates in the site.
So, maybe there is an issued with the known point coordinates that I input for control quality right?

------------------------------
Naufal Dwiakram
------------------------------

Original Message:
Sent: 05-11-2022 15:15
From: Sean Lahann
Subject: Point Out of Tolerance GNSS Processing

From what I can see in your report, the GPS observations have a higher quality rating than the control point coordinates for those same observed points, in all of the points. In other words the GPS vector solution produced a different coordinate (vertically) than the given coordinate. Without knowing exactly what you did and the other files associated to your project it is a little hard to make a call on what is the issue exactly. Your base could have the issue or possibly all your control coordinates are of low quality in the vertical. 

How was this survey done? Was it all static/rapid-static on known control points or unknowns. Did you start out with a control point file that you went and observed?

------------------------------
Sean Lahann, PLS
Phoenix, Arizona

Original Message:
Sent: 05-09-2022 19:47
From: Naufal Dwiakram
Subject: Point Out of Tolerance GNSS Processing

I don't know where I missed or entered the data incorrectly, but I did the same step on other data, and the data looks fine. Does this indicate that the observation data is poor and should be re-observed?

------------------------------
Naufal Dwiakram

Original Message:
Sent: 05-09-2022 08:47
From: Sean Lahann
Subject: Point Out of Tolerance GNSS Processing

Yes, the red flags appear because the point/coordinate "out-of-tolerance" in your settings is surpassed. If you went and changed those settings the flags would go away, but I don't recommend that. The original Global file you have there is a low accuracy point or unknown, was it a "here" start of the static file? I have had similar derivation reports, but usually all three are out and not just the vertical. In any case the GPS vectors seem to be working well with each other, so that leaves the first step to look at that Global coordinate, did something get entered incorrectly?

------------------------------
Sean Lahann, PLS
Phoenix, Arizona

Original Message:
Sent: 05-09-2022 00:07
From: Naufal Dwiakram
Subject: Point Out of Tolerance GNSS Processing

I'm sure that the coordinate system is correct. It work the red flag went away when I disable the global files, but I'm still confused about this issue. Does this happen because of the out-of-tolerance difference in vertical point coordinates between the original file from rinex and the baseline computation?

------------------------------
Naufal Dwiakram

Original Message:
Sent: 05-08-2022 22:02
From: Ronny Schneider
Subject: Point Out of Tolerance GNSS Processing

That has been discussed just a few days ago.
https://community.trimble.com/communities/community-homepage/digestviewer/viewquestion?ContributedContentKey=1ae7ef14-9992-45de-a287-c97ea4d3dfea&CommunityKey=d961b046-1661-40f3-8d7e-0bde6866a14d

Quoting Scot Roberts:
"A lot of times it's due to coordinates in the job file(s) from before the data was processed and they simply need to be removed or disabled so the observations can take over."

And that seems exactly what your point derivation report shows. Are you positive that your project is correctly setup, correct coordinate system and geoid?
If that is the case and you still see this error you'll have to disable the global coordinate that came with the static survey file, and re-compute the project (F4).
The resulting coordinates shouldn't change, since the observations should have taken precedence over the arbitrary coordinate from the static file. TBC just shows you that there is a large discrepancy between this coordinate and the one derived from base line processing and adjustment. Question is why it is that large? Hence my question about the correct project setup.


------------------------------
Ronny Schneider

Original Message:
Sent: 05-08-2022 19:54
From: Naufal Dwiakram
Subject: Point Out of Tolerance GNSS Processing

Hi,
I have processed the baseline for GNSS observations, the results of the baseline process have been fixed but there is a red mark for the vertical point tolerance. What do these red flags mean and how can I solve this problem?
This is the Point Derivation Report
Thanks


------------------------------
Naufal Dwiakram
------------------------------

Yes, I would start looking into that possibility. Check to make sure you didn't have a setup error or the control point has some how subsided. I would double check everything in the office before going back out to re-observe it. If you found that you had to go re-observe, then if possible set your base on a different control point as this will help figure out if your original control point has something wrong with it.

------------------------------
Sean Lahann, PLS
Phoenix, Arizona
------------------------------

Original Message:
Sent: 05-12-2022 00:04
From: Naufal Dwiakram
Subject: Point Out of Tolerance GNSS Processing

I did this survey for GCP measurement using rapid static method with 15 minutes observation. The control point using benchmark point that already known the coordinates in the site.
So, maybe there is an issued with the known point coordinates that I input for control quality right?

------------------------------
Naufal Dwiakram

Original Message:
Sent: 05-11-2022 15:15
From: Sean Lahann
Subject: Point Out of Tolerance GNSS Processing

From what I can see in your report, the GPS observations have a higher quality rating than the control point coordinates for those same observed points, in all of the points. In other words the GPS vector solution produced a different coordinate (vertically) than the given coordinate. Without knowing exactly what you did and the other files associated to your project it is a little hard to make a call on what is the issue exactly. Your base could have the issue or possibly all your control coordinates are of low quality in the vertical. 

How was this survey done? Was it all static/rapid-static on known control points or unknowns. Did you start out with a control point file that you went and observed?

------------------------------
Sean Lahann, PLS
Phoenix, Arizona

Original Message:
Sent: 05-09-2022 19:47
From: Naufal Dwiakram
Subject: Point Out of Tolerance GNSS Processing

I don't know where I missed or entered the data incorrectly, but I did the same step on other data, and the data looks fine. Does this indicate that the observation data is poor and should be re-observed?

------------------------------
Naufal Dwiakram

Original Message:
Sent: 05-09-2022 08:47
From: Sean Lahann
Subject: Point Out of Tolerance GNSS Processing

Yes, the red flags appear because the point/coordinate "out-of-tolerance" in your settings is surpassed. If you went and changed those settings the flags would go away, but I don't recommend that. The original Global file you have there is a low accuracy point or unknown, was it a "here" start of the static file? I have had similar derivation reports, but usually all three are out and not just the vertical. In any case the GPS vectors seem to be working well with each other, so that leaves the first step to look at that Global coordinate, did something get entered incorrectly?

------------------------------
Sean Lahann, PLS
Phoenix, Arizona

Original Message:
Sent: 05-09-2022 00:07
From: Naufal Dwiakram
Subject: Point Out of Tolerance GNSS Processing

I'm sure that the coordinate system is correct. It work the red flag went away when I disable the global files, but I'm still confused about this issue. Does this happen because of the out-of-tolerance difference in vertical point coordinates between the original file from rinex and the baseline computation?

------------------------------
Naufal Dwiakram

Original Message:
Sent: 05-08-2022 22:02
From: Ronny Schneider
Subject: Point Out of Tolerance GNSS Processing

That has been discussed just a few days ago.
https://community.trimble.com/communities/community-homepage/digestviewer/viewquestion?ContributedContentKey=1ae7ef14-9992-45de-a287-c97ea4d3dfea&CommunityKey=d961b046-1661-40f3-8d7e-0bde6866a14d

Quoting Scot Roberts:
"A lot of times it's due to coordinates in the job file(s) from before the data was processed and they simply need to be removed or disabled so the observations can take over."

And that seems exactly what your point derivation report shows. Are you positive that your project is correctly setup, correct coordinate system and geoid?
If that is the case and you still see this error you'll have to disable the global coordinate that came with the static survey file, and re-compute the project (F4).
The resulting coordinates shouldn't change, since the observations should have taken precedence over the arbitrary coordinate from the static file. TBC just shows you that there is a large discrepancy between this coordinate and the one derived from base line processing and adjustment. Question is why it is that large? Hence my question about the correct project setup.


------------------------------
Ronny Schneider

Original Message:
Sent: 05-08-2022 19:54
From: Naufal Dwiakram
Subject: Point Out of Tolerance GNSS Processing

Hi,
I have processed the baseline for GNSS observations, the results of the baseline process have been fixed but there is a red mark for the vertical point tolerance. What do these red flags mean and how can I solve this problem?
This is the Point Derivation Report
Thanks


------------------------------
Naufal Dwiakram
------------------------------

Attached are some comments to your point derivation report.

------------------------------
Sean Lahann, PLS
Phoenix, Arizona
------------------------------

Original Message:
Sent: 05-09-2022 19:47
From: Naufal Dwiakram
Subject: Point Out of Tolerance GNSS Processing

I don't know where I missed or entered the data incorrectly, but I did the same step on other data, and the data looks fine. Does this indicate that the observation data is poor and should be re-observed?

------------------------------
Naufal Dwiakram

Original Message:
Sent: 05-09-2022 08:47
From: Sean Lahann
Subject: Point Out of Tolerance GNSS Processing

Yes, the red flags appear because the point/coordinate "out-of-tolerance" in your settings is surpassed. If you went and changed those settings the flags would go away, but I don't recommend that. The original Global file you have there is a low accuracy point or unknown, was it a "here" start of the static file? I have had similar derivation reports, but usually all three are out and not just the vertical. In any case the GPS vectors seem to be working well with each other, so that leaves the first step to look at that Global coordinate, did something get entered incorrectly?

------------------------------
Sean Lahann, PLS
Phoenix, Arizona

Original Message:
Sent: 05-09-2022 00:07
From: Naufal Dwiakram
Subject: Point Out of Tolerance GNSS Processing

I'm sure that the coordinate system is correct. It work the red flag went away when I disable the global files, but I'm still confused about this issue. Does this happen because of the out-of-tolerance difference in vertical point coordinates between the original file from rinex and the baseline computation?

------------------------------
Naufal Dwiakram

Original Message:
Sent: 05-08-2022 22:02
From: Ronny Schneider
Subject: Point Out of Tolerance GNSS Processing

That has been discussed just a few days ago.
https://community.trimble.com/communities/community-homepage/digestviewer/viewquestion?ContributedContentKey=1ae7ef14-9992-45de-a287-c97ea4d3dfea&CommunityKey=d961b046-1661-40f3-8d7e-0bde6866a14d

Quoting Scot Roberts:
"A lot of times it's due to coordinates in the job file(s) from before the data was processed and they simply need to be removed or disabled so the observations can take over."

And that seems exactly what your point derivation report shows. Are you positive that your project is correctly setup, correct coordinate system and geoid?
If that is the case and you still see this error you'll have to disable the global coordinate that came with the static survey file, and re-compute the project (F4).
The resulting coordinates shouldn't change, since the observations should have taken precedence over the arbitrary coordinate from the static file. TBC just shows you that there is a large discrepancy between this coordinate and the one derived from base line processing and adjustment. Question is why it is that large? Hence my question about the correct project setup.


------------------------------
Ronny Schneider

Original Message:
Sent: 05-08-2022 19:54
From: Naufal Dwiakram
Subject: Point Out of Tolerance GNSS Processing

Hi,
I have processed the baseline for GNSS observations, the results of the baseline process have been fixed but there is a red mark for the vertical point tolerance. What do these red flags mean and how can I solve this problem?
This is the Point Derivation Report
Thanks


------------------------------
Naufal Dwiakram
------------------------------