-
Notifications
You must be signed in to change notification settings - Fork 8
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
Query 'active' networks without having to check every network in org #239
Comments
This issue would be partially addressed by a solution to #237. This would allow users such as @JenkeScheen to reduce the number of active Getting and setting relative weights of all How does this sound @JenkeScheen? |
that sounds perfect! |
@JenkeScheen were you able to make use of this feature in |
we ended up changing our method to adjusting existing network weights, see https://github.com/asapdiscovery/asapdiscovery/blob/main/asapdiscovery-alchemy/asapdiscovery/alchemy/cli/alchemy.py#L664-L684 |
I'll have a look around our API to see if we can improve anything with |
Excellent, thank you! |
I'm trying to build a function on top of
alchemiscale
that will allow me to find allweight
s associated with allnetwork
s that currently having 'running' or 'waiting'status
. With this function, I plan to build another function that will let mesubmit
networks toalchemiscale
with either higher priority than all 'waiting'/'running' networks, or instead with lower priority than all 'waiting'/'running' networks.Currently (AFAIK) the only way of doing this is by doing something like the below (as attempted in this PR):
which gives us all networks where
n_running
> 0 and/orn_waiting
> 0 (i.e. all networks that will still produce results). However,AlchemiscaleClient.query_networks()
will keep querying networks indefinitely until it has queried all networks ever run in our org which is very time consuming (due to back & forth requests toalchemiscale
) and unnecessary because these aren't important for this use-case.We're currently breaking the loop when 'enough' networks have been queried with 0/0 but this is a very janky solution. Ideally there would be a way to only query networks that have a 'finished' status or tag.
The text was updated successfully, but these errors were encountered: