Skip to content
This repository has been archived by the owner on Mar 28, 2024. It is now read-only.

[BUG-4182] [Improvement] The new cap to Avatar Render Weight needs to be done post trend calculation to accurately reflect data as well as large changes. #13177

Closed
2 tasks
sl-service-account opened this issue Oct 16, 2013 · 2 comments

Comments

@sl-service-account
Copy link

sl-service-account commented Oct 16, 2013

Information

As of server version 13.10.15.282406, ARW values sent by viewers are now capped at 500k before that value is factored into the trend data.
This pre-capping now causes an inaccurate trend.

This is now having an even more undesired affect of reflecting when >500k changes to ARW occur.

Example:

Someone thats been in a region a few minutes that has a ARW of 50k attaches a sculpt lagger that causes their ARW to jump to 3 million.

Pre-Trend Cap:
With the current pre-trend capped value, it would take over 20 minutes for their reported ARW to get near 500k.

Post-Trend Cap:
With the preferred post-trend capped value, their next reported ARW would be 500k because the 3 million would be the value factored into the trend data.

Please make the cap, post trend instead of before. Please allow the trend to accept values up to max integer/float. Thanks.

Links

Related

Original Jira Fields
Field Value
Issue BUG-4182
Summary [Improvement] The new cap to Avatar Render Weight needs to be done post trend calculation to accurately reflect data as well as large changes.
Type Bug
Priority Unset
Status Closed
Resolution Not Applicable
Reporter Lucia Nightfire (lucia.nightfire)
Created at 2013-10-16T19:01:21Z
Updated at 2017-06-07T13:40:12Z
{
  'Business Unit': ['Platform'],
  'Date of First Response': '2013-10-17T12:58:19.716-0500',
  'System': 'SL Simulator',
  'Target Viewer Version': 'viewer-development',
  'What just happened?': 'As of server version 13.10.15.282406, ARW values sent by viewers are now capped at 500k before that value is factored into the trend data.\r\nThis pre-capping now causes an inaccurate trend.\r\n\r\nThis is now having an even more undesired affect of reflecting when >500k changes to ARW occur.\r\n\r\nExample:\r\n\r\nSomeone thats been in a region a few minutes that has a ARW of 50k attaches a sculpt lagger that causes their ARW to jump to 3 million.\r\n\r\nPre-Capped Trend:\r\nWith the current pre-trend capped value, it would take over 20 minutes for their reported ARW to get near 500k.\r\n\r\nPost-Capped Trend:\r\nWith the preferred post-trend capped value, their next reported ARW would be 500k because the 3 million would be the value factored into the trend data.\r\n\r\nPleae make the cap, post trend instead of before. Please allow the trend to accept values up to max integer/float. Thanks.',
  'What were you doing when it happened?': '?',
  'What were you expecting to happen instead?': '?',
}
@sl-service-account
Copy link
Author

Lucia Nightfire commented at 2013-10-16T22:25:55Z, updated at 2013-10-17T06:25:45Z

My 20 minute estimate was way off as it would take probably 1.5 - 2 hours to get near 500k.

The following two passes were done with a target ARW >1.2 million, both values different from each other.
The second pass started after a 40 minute period of no change.

[13:03:23]: Target render weight is now 97910. Was -1
[13:04:29]: Target render weight is now 190700. Was 97910
[13:05:34]: Target render weight is now 248693. Was 190700
[13:06:40]: Target render weight is now 288373. Was 248693
[13:07:45]: Target render weight is now 317231. Was 288373
[13:08:50]: Target render weight is now 339164. Was 317231
[13:09:55]: Target render weight is now 356396. Was 339164
[13:11:01]: Target render weight is now 370293. Was 356396
[13:12:06]: Target render weight is now 381738. Was 370293
[13:13:11]: Target render weight is now 391327. Was 381738
[13:14:16]: Target render weight is now 399477. Was 391327
[13:15:22]: Target render weight is now 406490. Was 399477
[13:16:27]: Target render weight is now 412589. Was 406490
[13:17:32]: Target render weight is now 417940. Was 412589
[13:18:37]: Target render weight is now 422674. Was 417940
[13:19:42]: Target render weight is now 426892. Was 422674
[13:20:48]: Target render weight is now 430674. Was 426892
[13:21:53]: Target render weight is now 434083. Was 430674
[13:22:58]: Target render weight is now 437173. Was 434083
[13:24:03]: Target render weight is now 439986. Was 437173
[13:25:09]: Target render weight is now 442558. Was 439986
[13:26:14]: Target render weight is now 444919. Was 442558
[13:27:19]: Target render weight is now 447093. Was 444919
[13:28:24]: Target render weight is now 449102. Was 447093
[13:29:29]: Target render weight is now 450964. Was 449102
[13:30:34]: Target render weight is now 452695. Was 450964
[13:31:40]: Target render weight is now 454307. Was 452695
[13:32:45]: Target render weight is now 455814. Was 454307
[13:33:50]: Target render weight is now 457224. Was 455814
[13:34:55]: Target render weight is now 458547. Was 457224
[13:36:01]: Target render weight is now 459790. Was 458547
[13:37:06]: Target render weight is now 461088. Was 459790
[13:38:11]: Target render weight is now 462304. Was 461088
[13:39:16]: Target render weight is now 463446. Was 462304
[13:40:21]: Target render weight is now 464521. Was 463446
[13:41:26]: Target render weight is now 465641. Was 464521
[13:42:32]: Target render weight is now 466693. Was 465641
[13:42:32]: Target render weight is now 466693. Was 465641
[13:43:37]: Target render weight is now 467682. Was 466693

[13:57:22]: Target render weight is now 97910. Was -1
[14:37:41]: Target render weight is now 190700. Was 97910
[14:38:47]: Target render weight is now 248693. Was 190700
[14:39:54]: Target render weight is now 288373. Was 248693
[14:41:00]: Target render weight is now 317231. Was 288373
[14:42:05]: Target render weight is now 339164. Was 317231
[14:43:11]: Target render weight is now 356396. Was 339164
[14:44:18]: Target render weight is now 370293. Was 356396
[14:45:25]: Target render weight is now 381738. Was 370293
[14:46:30]: Target render weight is now 391327. Was 381738
[14:47:36]: Target render weight is now 399477. Was 391327
[14:48:43]: Target render weight is now 406490. Was 399477
[14:49:49]: Target render weight is now 412589. Was 406490
[14:50:55]: Target render weight is now 417940. Was 412589
[14:52:01]: Target render weight is now 422674. Was 417940
[14:53:07]: Target render weight is now 426892. Was 422674
[14:54:14]: Target render weight is now 430674. Was 426892
[14:55:20]: Target render weight is now 434083. Was 430674
[14:56:26]: Target render weight is now 437173. Was 434083
[14:57:33]: Target render weight is now 439986. Was 437173
[14:58:37]: Target render weight is now 442558. Was 439986
[14:59:43]: Target render weight is now 444919. Was 442558
[15:00:48]: Target render weight is now 447093. Was 444919

The importance of the data is in the change in trend. Which is why not capping the value entering the trend is important as currently, anything greater than 500k is trended the same way as these passes show since the data mirrors one another despite two different ARW values. Currently a value of 500k and 20 million will trend the same.

Agents entering a region start the trend at whatever ARW they have (capped at 500k).
It is vital that the trend reflect the change in values before any cap is used.

@sl-service-account
Copy link
Author

Simon Linden commented at 2013-10-17T17:58:20Z

FWIW the rate of change will also depend on the number of viewers making reports to the server.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

1 participant