
Reputation
Badges 1
151 × Eureka!Sorry for late reply, you mention there will be built-in way to version data. May I asked is there a release date for it?
conda create -n trains python==3.7.5
pip install trains==0.16.2.rc0
AgitatedDove14
I get this log but there is nothing show up in the UI.
2020-09-10 09:15:06,914 - trains.Task - INFO - Waiting for repository detection and full package requirement analysis ======> WARNING! UNCOMMITTED CHANGES IN REPOSITORY origin <====== 2020-09-10 09:15:10,378 - trains.Task - INFO - Finished repository detection and package analysis
I create a fresh conda env and install python for both machine
Btw, I am able to isolate the code that causing the problem. It maybe easier for you to debug.
` import numpy as np
import matplotlib
matplotlib.use('Agg')
import matplotlib.pyplot as plt
import seaborn as sns
from trains import Task
task = Task.init(project_name='examples', task_name='Matplotlib example')
x = [ 1,2,3]
y = [1,2,3]
x = list(x)
y = list(y)
f, ax = plt.subplots(figsize=(50, 0.7 * len(x)))
sns.barplot(y, x, orient="h", ax=ax)
plt.show() `
and the 8 charts are actually identical
In this case, I would rather use task.connect(), diff line by line is probably not useful for my data config. As shown in the example, shifting 1 line would result all remaining line different.
But this also mean I have to first load all the configuration to a dictionary first.
AgitatedDove14 No, unless I close the window manually.
Disable the matplotlib GUI does work.
Thanks Jake, I just upgraded our server to ClearML It works well and fixed some of the annoying UI bugs and enhancements. :)
I am not sure what's the difference of logging with "configuration" and "hyperparameters", for now , I am only using it as logging, I guess hyperparmeters has special meaning if I want to use "trains" for some other features.
AgitatedDove14
The core of Kedro is pipeline (multi-nodes), where you can stitch different pipeline together. For the data part, they use something called DataCatalog, which is a YAML file defined how your file is going to be saved/loaded, and where is the file. Kedro also resolve the DAGs of your pipeline, so you actually don't define what's the order of execution (it's defined by the input/output dependencies). The default is a sequentialRunner, optionally, you can use ParallelRunner where...
Is there a way to disable the iteration?
I have these steps in my plot and it create 8 iterations of the charts that create a lot of noise.
plt.plot([0, 1], [0, 1], color="navy", lw=lw, linestyle="--")
plt.xlim([0.0, 1.0])
plt.ylim([0.0, 1.05])
plt.xlabel("False Positive Rate")
plt.ylabel("True Positive Rate")
plt.title("Receiver operating characteristic example")
plt.legend(loc="lower right")
Ok, then maybe it can be still used as a data versioning solution. Except that I have to manually track the task id (those generate artifact) for versioning myself.
I see, I will look into the documentation of it, thanks Jake.
AgitatedDove14
are the data versioning completely different from the Trains Artifact/storage solution? or it's some enhanced feature.
one does record the package, the other does not
AgitatedDove14 Yes, as I found as Kedro's pipeline start running, the log will not be sent to the UI Console anymore. I tried both Task.init before/after the start of kedro pipeline and the result is the same. The log is missing, but the Kedro logger is print to sys.stdout in my local terminal.
Ok, will prepare a PR and script to reproduce the error
I want the support for click as well, or is there any adhoc solution?
I have been using this line to prevent experiments won't accidentally sent to the public server (I have my custom self-hosted server)Task.set_credentials("PLACEHOLDER", "PLACEHOLDER","PLACEHOLDER")
However, when I upgraded from 0.17.5 -> > 1.0.0. Weird stuff happen.
Since upgrade from v0.17.5 -> > 1.0.0, it has issue replacing the credentials.
Expected Behavior:
Conf should replace the "PLACEHOLDER" is the conf file exist. Else it should fails the experiment.
What happened:
The ...
as I have wandb docker set up on the same VM for teting
I think it's related to the fix that use "incremental: true", this seems to fix 1 problem, but at the same time it will ignore all other handlers.