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

compactTree view 'Q' links a depth too high #739

Open
matiroy opened this issue Sep 15, 2019 · 4 comments
Open

compactTree view 'Q' links a depth too high #739

matiroy opened this issue Sep 15, 2019 · 4 comments

Comments

@matiroy
Copy link
Contributor

matiroy commented Sep 15, 2019

(or maybe that's on purpose?)

it brings us to the parent question instead of the workspace of the question it's associated with

example
from https://mosaic.ought.org/w/4268/compactTree?expanded=true

clicking here:
image

brings us here: https://mosaic.ought.org/w/d766aef8-e381-4ed8-b324-de5b108daa6d

instead of here: https://mosaic.ought.org/w/b196e09b-6e09-4df9-92cf-0e7fe6d3c25a

@zjmiller
Copy link
Contributor

Hmm yeah I agree this seems off, but where should the "Q" bring you while we're waiting for the honest or malicious response, or if the malicious expert declines?

@matiroy
Copy link
Contributor Author

matiroy commented Sep 16, 2019

I'd say nothing

@matiroy
Copy link
Contributor Author

matiroy commented Sep 19, 2019

David says:

For a completed tree, Is there a way to view the judge's scratchpad notes if there were no followup questions to a subquestion? Clicking on the "Q" for the judge's workspace effectively takes me one level up and I'm not sure if I'm missing a button

https://ought-inc.slack.com/archives/CL6PLP82J/p1568595899015500

@matiroy
Copy link
Contributor Author

matiroy commented Oct 4, 2019

Williams Sells would really like if this was changed.

I'm sure there's already an Issue on the Mosaic Github for this, but man, figuring out "where" Judges operate in an experiment was a huge stumbling block for me initially and this in particular definitely didn't help me.

Temporary solution:

Is there not a better way to find the deepest Judge workspace other than...
From the tree view, clicking on one of the deepest visible workspaces, clicking 'Subtree >>', and then clicking 'show 1 subtree' like 3 times until you finally find the right workspace?

source: https://ought-inc.slack.com/archives/CLHBPR4JV/p1570141163054900

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants