matt-erhart / lab Goto Github PK

View Code? Open in Web Editor NEW

2.0 2.0 3.0 12.75 MB

TypeScript 15.18% JavaScript 82.61% CSS 0.31% Python 1.89%

lab's People

Contributors

Stargazers

Watchers

Forkers

xeniaqian94 featuretogglestudy joelchan

lab's Issues

create "experimental conditions"

Create versions of the app where:

Context cannot be expanded at all
Context can be expanded, but not adjusted
Jump back to PDF from context is disabled

enable logging for experiments

Enable write to some file

Possible schema
- userID
- Version / condition
- Active paper
- Type
- Descr / content
- Start
- Stop
- Duration

Generally want to know

How long is it taking people to
- "select context"
- "write a claim"
- "any other context attachments"
- do the whole task
How often are people
- Editing their claims
- Moving things around

Possible types of events to log:

Selections (init + drag + stop)
Keystrokes
- Focused node id
- Starting text
- Ending text
"Endpoints" for creating claims (x-ing out)
Overall time on task

Question: async handling on pdf.publication node and auto-grab info/node

A question to Matt: How do we allow auto-grab HTTP request to happen in the back-end, so that it does not delay the immediate process of nodes of type pdf.publication being rendered and initiated.

If it's possible, then how could we check back in-time when the HTTP request has finished, state.json being updated so we could subsequent do following tasks like new in-line highlights or render auto-grab nodes?

This relates to the code block in line 100-130

lab/src/renderer/App.tsx

Lines 100 to 130 in 3e4b423

 }); 

 const autograbNodes = pdfDirs.map((dir, ix) => { 

 return makeAutograbNode( 

 dir, 

 { dir }, 

 { x: 50 + ix + Math.random() * 100, y: 50 + ix * Math.random() * 100 } 

 ); 

 }); 

 const allNodeIds = Object.keys(nodes); 

 const newPubs = pdfNodes.filter(pdfNode => !allNodeIds.includes(pdfNode.id)); //filter out nodes that exists 

 const newAutograbs = autograbNodes.filter( 

 autograbNode => !allNodeIds.includes(autograbNode.id) 

 ); //filter out nodes that exists 

 // add links btw nodes of type auto-grab and nodes of pdf.publication 

 let newLinks = []; 

 for (let i = 0; i < newPubs.length; i++) { 

 const linkToPdf = makeLink(newPubs[i].id, newAutograbs[i].id, { 

 type: "more" 

 }); 

 newLinks.push(linkToPdf); 

 // assert each paper corresponds to one autograb node and idx are the same(for now) 

 } 

 // concatenate nodes of type auto-grab and nodes of pdf.publication 

 let newNodes = [] as aNode[]; 

 const nodesArray = newPubs.concat(autograbNodes); 

 for (let i = 0; i < nodesArray.length; i++) {

How can the risk of feature toggle technical debt be reduced?

Dear developers,

I, Rezvan Mahdavi Hezaveh ([email protected]), and my colleague, Nirav Ajmeri ([email protected]), software engineering researchers from North Carolina State University are conducting an academic study of feature toggles and technical debt.

In our investigations on GitHub repositories, we noticed that you are using feature toggles in your repository. For instance, this file is used to define feature toggles and their values.

We would appreciate your collaboration in this study by answering an anonymous survey based upon your experience with the feature toggles. This survey has 20 questions and the estimated time to answer these questions is 10 minutes.

The link to the survey is here: https://ncsu.qualtrics.com/jfe/form/SV_5BGE3wNDUtFQqMd

Once you start answering the survey questionnaire, you will have 24 hours to finish it.
As an appreciation for your time, we will conduct a random drawing and give $25 Amazon gift cards to five selected survey respondents. Also, we will share our results with you.

Thanks

Quality of life fix, signifier?

Suggested from user deployment

On the left panel, while zooming in/out on the PDF, maybe center on the cursor position
Pre-load the claim map with min zoom scale (so all claims are showing up and users would know some claims are there)

matt-erhart / lab Goto Github PK

lab's People

Contributors

Stargazers

Watchers

Forkers

lab's Issues

create "experimental conditions"

enable logging for experiments

Question: async handling on pdf.publication node and auto-grab info/node

How can the risk of feature toggle technical debt be reduced?

Quality of life fix, signifier?

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 autograbNodes = pdfDirs.map((dir, ix) => {
	return makeAutograbNode(
	dir,
	{ dir },
	{ x: 50 + ix + Math.random() * 100, y: 50 + ix * Math.random() * 100 }
	);
	});

	const allNodeIds = Object.keys(nodes);

	const newPubs = pdfNodes.filter(pdfNode => !allNodeIds.includes(pdfNode.id)); //filter out nodes that exists
	const newAutograbs = autograbNodes.filter(
	autograbNode => !allNodeIds.includes(autograbNode.id)
	); //filter out nodes that exists

	// add links btw nodes of type auto-grab and nodes of pdf.publication
	let newLinks = [];
	for (let i = 0; i < newPubs.length; i++) {
	const linkToPdf = makeLink(newPubs[i].id, newAutograbs[i].id, {
	type: "more"
	});
	newLinks.push(linkToPdf);
	// assert each paper corresponds to one autograb node and idx are the same(for now)
	}

	// concatenate nodes of type auto-grab and nodes of pdf.publication
	let newNodes = [] as aNode[];
	const nodesArray = newPubs.concat(autograbNodes);
	for (let i = 0; i < nodesArray.length; i++) {