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

SpotDisplay class #2

Open
tischi opened this issue Sep 23, 2022 · 7 comments
Open

SpotDisplay class #2

tischi opened this issue Sep 23, 2022 · 7 comments

Comments

@tischi
Copy link

tischi commented Sep 23, 2022

Hi @constantinpape,

I think it would make sense for SpotDisplay to extend AnnotationDisplay:

public abstract class AnnotationDisplay< A extends Annotation > extends AbstractDisplay< AnnotationType< A > >
{
	// Serialization
	protected String lut = LUTs.GLASBEY;
	protected String colorByColumn;
	protected Double[] valueLimits;
	protected boolean showScatterPlot = false;
	protected String[] scatterPlotAxes = new String[]{ ColumnNames.ANCHOR_X, ColumnNames.ANCHOR_Y };
	protected List< String > tables; // column chunks to display
	protected boolean showTable = true;
	protected boolean showAsBoundaries = false;
	protected float boundaryThickness = 1.0F;
	protected int randomColorSeed = 42;

Do you envision to also support all those field in the JSON spec of spotDisplay?

@tischi
Copy link
Author

tischi commented Sep 23, 2022

do we want to add a selectedSpotIds?

@constantinpape
Copy link
Contributor

I think it would make sense for SpotDisplay to extend AnnotationDisplay:

Yes, I agree.

protected boolean showAsBoundaries = false;
protected float boundaryThickness = 1.0F;

These two don't make sense for spots. All the others do make sense.

do we want to add a selectedSpotIds?

Yes!

@tischi
Copy link
Author

tischi commented Sep 25, 2022

These two don't make sense for spots. All the others do make sense.

  1. I am not so sure. I can be nice to see what's behind a spot. I think this can be very useful for visual QC to see whether there actually is a spot signal "inside" the spot.

  2. I think we need something to specify how large the spots should be rendered. Maybe spotRadius?

@constantinpape
Copy link
Contributor

constantinpape commented Sep 25, 2022

  1. I am not so sure. I can be nice to see what's behind a spot. I think this can be very useful for visual QC to see whether there actually is a spot signal "inside" the spot.

Ok, that's a good point. We can keep the showAsBoundaries and boundaryThickness then.

2. I think we need something to specify how large the spots should be rendered. Maybe spotRadius?

Yep, I also just thought about this. spotRadius is a good name for it.

@constantinpape
Copy link
Contributor

And I guess spotRadius is given in physical units?!

@tischi
Copy link
Author

tischi commented Sep 26, 2022

I would say so, yes, in the units of the project.

@constantinpape
Copy link
Contributor

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