Ticket #6 (closed Verified Error: Fixed)
Mistake in treating Rmax for VR-WT
| Reported by: | arturas | Owned by: | cp |
|---|---|---|---|
| Priority: | Critical | Milestone: | 3.1.40 |
| Component: | Positioning of elements | Version: | |
| Keywords: | WT simulation radius | Cc: | |
| Blocked By: | Blocking: | ||
| Estimated Number of Hours: | Pending: | ||
| Add Hours to Ticket: | Total Hours: | ||
| Original Estimate: | Source (can be left blank): | ||
| Must be closed before next release: | Effort Required: |
Description
The problem noted in ver. 3.1.38 which was not noticed in earlier versions, when previously running the same scenario (original mail from K. Loew below).
Investigation confirmed the problem. Analysis of log-file shows that the problem is linked to calculation of VR-WT simulation radius. Based on noise-limted network settings, the programme calculates R=2.93 km, as is displayed if consulting Results/Radiuses? part of tree-view, but during the snapshots this is overriden somehwere in the programme and the Rmax is assigned 0 km value. Subsequently in all trials the VR-WT distance is 0.
BR, Arturas
Attachments
-
Gsm-Tetra.txt
(8.5 KB) -
added by arturas 5 years ago.
- Scenario file (SMC-2)
-
SEAMCAT version 3...38.txt
(2.2 KB) -
added by arturas 5 years ago.
- E-mail from K. Loew
Change History
Changed 5 years ago by arturas
-
attachment
Gsm-Tetra.txt
added
comment:1 follow-up: ↓ 2 Changed 5 years ago by cp
- Owner changed from cp to arturas
Do we know which version he used last? Is this something introduced in 3.1.38 or perhaps ealier?
comment:2 in reply to: ↑ 1 Changed 5 years ago by arturas
Replying to cp:
Do we know which version he used last? Is this something introduced in 3.1.38 or perhaps ealier?
In his mail Karl refers to the previous version from "spring", I would have guessed it could been 3.1.37.
Scenario file (SMC-2)