Divisi UI

Output information dissapears after I click in SVD

Asked by Kyle Drexel

When I perform an analysis on data with a canonical narrative I get a great report of congruence / consistency - but when I click on the SVD view the output pane seems to reset and go blank. I expected this to be a scrolling "history" of output for the session, with information that is persistent

Question information

Language:
English Edit question
Status:
Answered
For:
Divisi UI Edit question
Assignee:
No assignee Edit question
Last query:
Last reply:

This question was originally filed as bug #433218.

Revision history for this message
Kyle Drexel (kydrex) said : 		#1

Interestingly, if I click on the point in the SVD view that represents the canonical narrative, the output data re-appears. This was unexpected. So, apparently, the output window is somehow tied to what his selected in the SVD view?

Revision history for this message
Rob Speer (rspeer) said : 		#2

Turning this into a question about workflow in the interface.

Revision history for this message
Rob Speer (rspeer) said : 		#3

The main purpose of the output window, actually, is to show information about the selected point in the SVD view. The fact that status and error messages from Divisi get stuck on the end of the window is a kind of side purpose.

One of the most useful kinds of information to show is when you select a canonical document, because the information includes consistency and congruence. Knowing this would be useful, in fact, we made it select the first canonical document by default.

This means that the relevant information is persistent for as long as the SVD result is, as it's attached to points in the SVD space. The Divisi output isn't persistent -- we made the assumption that it would only be useful if Divisi crashed, in which case it would still be there. Is there still a need to keep a log of this kind of output?

Can you help with this problem?

Provide an answer of your own, or ask Kyle Drexel for more information if necessary.

To post a message you must log in.