Hello.
I used the command in the format: gpdcreport file.report -best 100 | gpprofile -average-at 30 > out.txt.
The purpose was to get Vs30 for the top 100 Vs profiles with lowest misfit. I usd this also for other depths such as 5 m, 10 m and 20 m. In all cases, the output file showed exactly same values. When I checked, I found that in all files, instead of Vs_average values, it is just giving the Vs in the top layer, as inferred form the file Vs_profiles.txt. The I used the command gpec8 to calculate vs30 values and it gave correct values, which are different values compared to the above using -average-at-30.
I have attached all the required files. I request you to kindly look into the matter the correct the use of -average-at-x command.
gpprofile for -average-at-30
-
- Posts: 13
- Joined: Sun Jan 24, 2021 11:11 am
gpprofile for -average-at-30
- Attachments
-
- Vs10.txt
- (5.31 KiB) Downloaded 651 times
-
- Vs20.txt
- (5.31 KiB) Downloaded 622 times
-
- Vs_profiles.txt
- (88.42 KiB) Downloaded 663 times
-
- gpec.txt
- (5.99 KiB) Downloaded 622 times
-
- Vs30.txt
- (5.31 KiB) Downloaded 637 times
Re: gpprofile for -average-at-30
Which release number are you running?
I checked on the latest (3.5.0-preview and 3.4.1), I get the same result for gprofile -average-at 30 and gpec8:
I remember that I fixed a similar error but long time ago.
I checked on the latest (3.5.0-preview and 3.4.1), I get the same result for gprofile -average-at 30 and gpec8:
Code: Select all
$ cat /tmp/toto
4
2.5480569802562365034 342.28209375687021065 153.01500000000001478 2000
21.603881357787759754 898.58142499807229342 159.22802259015003301 2000
34.4169038301121617 2093.5059925194091193 256.71157031765238798 2000
0 2406.4311536594955214 1065.1282273573376642 2000
$ cat /tmp/toto | gpec8
Vs30 171.319 Class D
$ cat /tmp/toto | gpprofile -average-at 30
# Vs
171.319
-
- Posts: 13
- Joined: Sun Jan 24, 2021 11:11 am
Re: gpprofile for -average-at-30
Thanks for the prompt reply.
I am using the latest 3.4.1 Geopsy and DINVER but the MSYS is of older version, so probably due to that, this is occurring. But, when I installed newer MSYS version, it showed some issues. What can be done?
I am using the latest 3.4.1 Geopsy and DINVER but the MSYS is of older version, so probably due to that, this is occurring. But, when I installed newer MSYS version, it showed some issues. What can be done?