Skip to content
This repository has been archived by the owner on Sep 21, 2022. It is now read-only.

Disallow multi-submission usage of private randomized components #268

Open
Shoeboxam opened this issue Jun 28, 2020 · 0 comments
Open

Disallow multi-submission usage of private randomized components #268

Shoeboxam opened this issue Jun 28, 2020 · 0 comments

Comments

@Shoeboxam
Copy link
Member

Randomized components have a different value every time they are run. At this point, the only randomized private component is the even partition. Unfortunately, you can extend partitioned portions of the graph across multiple submissions. In this case, you may be expecting the same underlying partition, but since the even partition is private, it is not stored, and is thus recomputed every submission. This can lead you to unintentionally match up statistics from different random partitions, trashing results.

Alternatively, provide a way of caching the node. But to do node caching right, we'd ideally need to persist to the filesystem, because partitions are typically run before aggregation.

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

No branches or pull requests

1 participant