Skip to content

Support parsing HyperlocalExperiment #276

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

Mygod
Copy link
Contributor

@Mygod Mygod commented Mar 30, 2025

Fixes #272.

@jfberry
Copy link
Collaborator

jfberry commented Mar 30, 2025

Thanks for your contribution. I've got some questions about this that I hope you can help me with before any formal review

  • What is the purpose of storing this detail in golbat? Are the spawns captured conventionally and this is just "for information"? How would the information usefully be consumed or displayed in third party tools?
  • This looks like it is per map cell, what range do you get to see this in a GMO (eg only when you are on top of it, or from distance?) This will impact the number of times these values are seen and with no cache in front of it, the number of round trips to the database
  • Is the experiment id re-used for different activations? Do the timings get updated? How far in advance of being activated does this get seen?
  • Is there sense in keeping the data long term? (I note that there is no expiry on data retention)

@Mygod
Copy link
Contributor Author

Mygod commented Mar 30, 2025

  • What is the purpose of storing this detail in golbat? Are the spawns captured conventionally and this is just "for information"? How would the information usefully be consumed or displayed in third party tools?

Spawns are captured conventionally but will be impacted by whether they are in the region or outside. In the past (during elite/t4 raid bonus), extra spawnpoints are activated inside the region and the spawn is drawn from a different pool. All the changes are reverted after the timer expires. It's like a mini-event but only for spawns (/players?) inside the circle.

ReactMap could display these circles and Poracle could probably alert the player that a tracked spawn is inside the bonus region and is subject to change after the region expires/reactivates.

  • This looks like it is per map cell, what range do you get to see this in a GMO (eg only when you are on top of it, or from distance?) This will impact the number of times these values are seen and with no cache in front of it, the number of round trips to the database

This could be in-memory only like Pokemon since they are all short lived. No idea about distance.

  • Is the experiment id re-used for different activations? Do the timings get updated? How far in advance of being activated does this get seen?

ID (3578) + challenge key (spawn_wild_bug_types) + event radius (100m) is the same across all rows for this event and I suspect that this would continue to be the case. I imagine experiment ID is actually a global value that is also used for global event toggles as well and challenge key is probably the key for the in-game bonus text displayed to the player.

  • Is there sense in keeping the data long term? (I note that there is no expiry on data retention)

No. This should be treated like Pokemon table.

@jfberry
Copy link
Collaborator

jfberry commented Mar 30, 2025

On the first point, I can see it being useful if we can determine the change time (either it's going to change, or it's going to change back). The "going to change" might be difficult for us to determine although it's likely s2 related rather than exactly circular. I wonder if there is anything on the spawn that indicates it is associated with the experiment that would allow correlation

@Mygod
Copy link
Contributor Author

Mygod commented Mar 30, 2025

I don't think there is but I haven't checked, and I believe it could be exactly circular given the small radius (I think the biggest radius was 300m?).

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

Successfully merging this pull request may close these issues.

Hyperlocal experiments support
2 participants