You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I use usually a "prefix" to assign an ID that depends on the type of experiment, but the ID should be assigned automatically. However, I don't see where used IDs are stored. They seem to be on a queue, but there's no way to see which ones have been used already.
A simple query to redis should take care of that... IDs would be automatically assigned using auto-increment together with the prefix.
The text was updated successfully, but these errors were encountered:
In EvoSpace for instance, I just used a prefix plus a timestamp, is short and sequential. For other lower level IDs like WorkerID or MessageID, we generate a UUID.
The other idea is to have a settings.py file where each advanced user can generate the JSON as he pleases. For instance, we can have a python dictionary with an EXPERIMENT_ID key:
I use usually a "prefix" to assign an ID that depends on the type of experiment, but the ID should be assigned automatically. However, I don't see where used IDs are stored. They seem to be on a queue, but there's no way to see which ones have been used already.
A simple query to redis should take care of that... IDs would be automatically assigned using auto-increment together with the prefix.
The text was updated successfully, but these errors were encountered: