Skip to content
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

Unable to visualize table in OutputViewer #489

Closed
StefanoFioravanzo opened this issue Dec 6, 2018 · 14 comments · Fixed by #4236
Closed

Unable to visualize table in OutputViewer #489

StefanoFioravanzo opened this issue Dec 6, 2018 · 14 comments · Fixed by #4236

Comments

@StefanoFioravanzo
Copy link
Member

I am trying to visualize some artifacts in the OutputViewer with no success.
I have the following metadata.json file in the root of the container's file system:

{
	"version": 1,
	"outputs": [{
		"type": "table",
		"source": "/linear_model_metrics.csv",
		"header": ["Epoch", "Loss_te", "Acc", "Loss_tr"],
		"format": "csv"
	}]
}

The file linear_model_metrics.csv is in the file system root as well. Comma separated with first line as header. In the Pipelines UI I have a blank page in the Artifacts tab, no errors thrown.

@yebrahim
Copy link
Contributor

yebrahim commented Dec 7, 2018

Currently, the Pipelines UI reads the artifact data from the storage service directly, and only GCS and minio are supported at the moment, adding support for more services is welcome of course. If your data is on GCS, the source field should be a gs://... path.

We are currently exploring better ways to mount/read this data such that it's easier to keep the data in the cluster, or in other types of storage.

/cc @Ark-kun.

@StefanoFioravanzo
Copy link
Member Author

Thank you for the response. For sure it would be helpful to be able to load files directly from the container's local file system. Any info regarding the timeline or priorities on these features?

@IronPan
Copy link
Member

IronPan commented Dec 7, 2018

@StefanoFioravanzo Just wondering did you mount the volume through the container Op, and writes linear_model_metrics.csv to it directly?

@StefanoFioravanzo
Copy link
Member Author

@IronPan I mounted the volume like you suggested in #477 . And yes I wrote linear_model_metrics.csv directly form the container.

@swiftdiaries
Copy link
Member

Is this still the case?
Does the source field have to be either in GCS or minio?

@SinaChavoshi
Copy link
Contributor

+1 on supporting local mount. This is absolutely necessary for on-prem deployment. I'm loading the data to an nfs volume in preprocessing, training steps ... would be great to read it to tensor-board directly from there.

@jinchihe
Copy link
Member

+1 for supporting local storage mounted from PersistentVolume.

@zwqjoy
Copy link

zwqjoy commented Mar 6, 2019

+1 for supporting local storage mounted from PersistentVolume or Volume

@stale
Copy link

stale bot commented Jun 24, 2020

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

@stale stale bot added the lifecycle/stale The issue / pull request is stale, any activities remove this label. label Jun 24, 2020
@stale
Copy link

stale bot commented Jul 1, 2020

This issue has been automatically closed because it has not had recent activity. Please comment "/reopen" to reopen it.

@stale stale bot closed this as completed Jul 1, 2020
@Dhaval08
Copy link

Any update on this? +1 for support for local sources

@Bobgy
Copy link
Contributor

Bobgy commented Aug 5, 2020

/reopen

@k8s-ci-robot k8s-ci-robot reopened this Aug 5, 2020
@k8s-ci-robot
Copy link
Contributor

@Bobgy: Reopened this issue.

In response to this:

/reopen

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

@stale stale bot removed the lifecycle/stale The issue / pull request is stale, any activities remove this label. label Aug 5, 2020
@Bobgy
Copy link
Contributor

Bobgy commented Aug 5, 2020

#4236 supports this feature request.

Linchin pushed a commit to Linchin/pipelines that referenced this issue Apr 11, 2023
…n test grid by name (kubeflow#490)" (kubeflow#493)" (kubeflow#494)

This reverts commit 81326be.

* Relates to kubeflow#489

* Roll forward the orginal change now that kfctl_create_e2e_workflow.py
  has been updated to handle the extra argument.

add a leading /
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment