Hi, I've followed the steps provided in dodrio-data-gen.

Hi <a class="user-mention notranslate" data-hovercard-type="user" data-hovercard-url="

Yes, <a class="user-mention notranslate" data-hovercard-type="user" data-hovercard-url

<a class="user-mention notranslate" data-hovercard-type="user" data-hovercard-url="/us

Got it working! <a target="_blank" rel="noopener noreferrer nofollow" href="https:

Issue when attempting to visualize custom dataset,about poloclub/dodrio

xiaohk commented on May 22, 2024

Hi @Fquico1999, thanks for trying out Dodrio!

Do you get any error in the browser console?

For example, if you use chrome, you can open the web console by following these instructions.

from dodrio.

Fquico1999 commented on May 22, 2024

Yes, @xiaohk I do see some errors,

Im not very experienced with js or d3, so I'll attempt to debug and report here with any results.
In the meantime, if you have any ideas what this could be, please let me know

from dodrio.

xiaohk commented on May 22, 2024

It seems one of the data variables (headOrderMap.syntactic, headOrderMap.semantic , or headOrderMap.important) is not initialized (undefined). You can try to print out these variables in before the error line, e.g. console.log(headOrderMap).

Good luck! Keep us updated.

dodrio/src/dependency-view/Dependency.svelte

Lines 724 to 762 in 9da674b

    
             const initData = async (dependencyFile, saliencyFile, syntacticOrderFile, 
        
               semanticOrderFile, importantOrderFile) => { 
        
               // Init dependency data 
        
               data = await d3.json(dependencyFile); 
        
               data = data[instanceID]; 
        
               let relationCounter = new Map(); 
        
               selectedRelations = {}; 
        
               // Create a set of existing [parent, child] pairs 
        
               existingLinkSet = new Map(); 
        
               data.list.forEach(d => { 
        
                 existingLinkSet.set(String([d.parent, d.child]), d.relation); 
        
                 if (relationCounter.has(d.relation)) { 
        
                   relationCounter.set(d.relation, relationCounter.get(d.relation) + 1); 
        
                 } else { 
        
                   relationCounter.set(d.relation, 1); 
        
                   // Select all relations in initialization 
        
                   selectedRelations[d.relation] = true; 
        
                 } 
        
               }); 
        
               relationCounter = new Map([...relationCounter.entries()].sort((a, b) => b[1] - a[1])); 
        
               relations = [...relationCounter.entries()]; 
        
               // Init saliency data 
        
               saliencies = await d3.json(saliencyFile); 
        
               saliencies = saliencies[instanceID]; 
        
               // Init the dependency layer/head accuracy list 
        
               headOrderMap.syntactic = await d3.json(syntacticOrderFile); 
        
               headOrderMap.semantic = await d3.json(semanticOrderFile); 
        
               headOrderMap.semantic = headOrderMap.semantic[instanceID]; 
        
               headOrderMap.important = await d3.json(importantOrderFile); 
        
               headOrderMap.important = headOrderMap.important[instanceID]; 
        
             };

from dodrio.

Fquico1999 commented on May 22, 2024

@xiaohk It seems like the problem arises when trying to access the index instanceID. Since my dataset has less elements than 1562, it returns undefined for several parameters.
I've seen references and definitions of instanceID in several locations, where would be the best place to change it?

from dodrio.

Fquico1999 commented on May 22, 2024

Got it working!

The problem was the one describe above, instanceID is defined in several files to be 1562, and needs to be changed to an index that exists in the dataset. Once that was changed, it seems to work.

I believe it would be useful to have instanceID defined in a single accessible location. Or if that is not possible, then perhaps changing it to 1 under the assumption that most datasets are at least length 1.

from dodrio.

Issue when attempting to visualize custom dataset about dodrio HOT 5 CLOSED

Comments (5)

Related Issues (8)

Recommend Projects

React

Vue.js

Typescript

TensorFlow

Django

Laravel

D3

Recommend Topics

javascript

web

server

Machine learning

Visualization

Game

Recommend Org

Facebook

Microsoft

Google

Alibaba

D3

Tencent

	const initData = async (dependencyFile, saliencyFile, syntacticOrderFile,
	semanticOrderFile, importantOrderFile) => {
	// Init dependency data
	data = await d3.json(dependencyFile);
	data = data[instanceID];

	let relationCounter = new Map();
	selectedRelations = {};

	// Create a set of existing [parent, child] pairs
	existingLinkSet = new Map();

	data.list.forEach(d => {
	existingLinkSet.set(String([d.parent, d.child]), d.relation);
	if (relationCounter.has(d.relation)) {
	relationCounter.set(d.relation, relationCounter.get(d.relation) + 1);
	} else {
	relationCounter.set(d.relation, 1);
	// Select all relations in initialization
	selectedRelations[d.relation] = true;
	}
	});
	relationCounter = new Map([...relationCounter.entries()].sort((a, b) => b[1] - a[1]));
	relations = [...relationCounter.entries()];

	// Init saliency data
	saliencies = await d3.json(saliencyFile);
	saliencies = saliencies[instanceID];

	// Init the dependency layer/head accuracy list
	headOrderMap.syntactic = await d3.json(syntacticOrderFile);

	headOrderMap.semantic = await d3.json(semanticOrderFile);
	headOrderMap.semantic = headOrderMap.semantic[instanceID];

	headOrderMap.important = await d3.json(importantOrderFile);
	headOrderMap.important = headOrderMap.important[instanceID];

	};