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
We have also released our own REST API at comet.ml BTW. If we can do anything there so you don't have to maintain this, let us know! https://www.comet.ml/docs/python-sdk/Comet-REST-API/ Or, if there is anything we can add to better support yours, let us know that too!
Thanks for the note! I'll make sure to take a look at the official Python API before making any updates here; that probably won't be right away, though, as I'm busy with other things. From a quick glance over the page you linked, it looks like it would be good for me to let your library handle the lower-level calls to the REST endpoints so that I don't duplicate the work there and because your library will be better maintained when there are updates.
I'll probably keep this library around for higher-level calls, unless you're interested in PRs to add functionality to your library (well, not exactly a PR if it's closed-source, but I could send reference implementations). I understand that what higher-level functions one wants could get too specific for different users, though. For me, for example, the most common use case is wanting to get all experiments that match some query based on their hyperparameters and then return certain metrics from those experiments in a dataframe that can easily be aggregated and plotted. Once the charting in Comet can handle aggregating experiments, I probably won't use this library much myself either.
Activity
dsblank commentedon Jan 14, 2019
We have also released our own REST API at comet.ml BTW. If we can do anything there so you don't have to maintain this, let us know! https://www.comet.ml/docs/python-sdk/Comet-REST-API/ Or, if there is anything we can add to better support yours, let us know that too!
neighthan commentedon Jan 14, 2019
Thanks for the note! I'll make sure to take a look at the official Python API before making any updates here; that probably won't be right away, though, as I'm busy with other things. From a quick glance over the page you linked, it looks like it would be good for me to let your library handle the lower-level calls to the REST endpoints so that I don't duplicate the work there and because your library will be better maintained when there are updates.
I'll probably keep this library around for higher-level calls, unless you're interested in PRs to add functionality to your library (well, not exactly a PR if it's closed-source, but I could send reference implementations). I understand that what higher-level functions one wants could get too specific for different users, though. For me, for example, the most common use case is wanting to get all experiments that match some query based on their hyperparameters and then return certain metrics from those experiments in a dataframe that can easily be aggregated and plotted. Once the charting in Comet can handle aggregating experiments, I probably won't use this library much myself either.
dsblank commentedon Jan 14, 2019
Probably best would be to send descriptions of behaviors (or syntax) that you would like, if we don't support that already.
We also have a query API planned that will allow fast, specific searches from the SDK, and more advanced charting options from the UI. Stay tuned!