pmelchior / des-exp-checker Goto Github PK

When the viewer request an image that the server doesn't know, db.php will return

name: "getImage.php?name="

instead of a Server Error, so that the $.post function cannot execute the .fail() part. Update db.php and check that failure triggers a message popup to explain that to the user.

I was trying to signup as the new user and the signup modal is getting freeze.

I've seen that sometimes bleed trails are not fully masked. Also bad columns sometimes aren't masked over the whole of the column badness.

I think these options should be another named problem. Maybe "Incomplete masking of bleed trail or bad column".

Simple thumbs up / thumbs down for gallery objects. Order the entries according to most +1.

Requires:

• extra column for thumb icons
• database to store the user submissions
• update to gallery.php to record the submissions

Would benefit from MVC data model to generate the table from json results and to attach the correct event handler to thumb icons.

Can be used to show the "hottest object" on index.html with stats from the last week/month.

The image is fully specified with only expname= and ccd= in the POST. The band is implied by expname. Currently the POST is requiring band to work.

I've seen a number of images where the CCD tape points are not corrected for. It would be nice if this was a named problem.

When viewing "My Statistics", the number of images required to reach chief inspector is given as the negative of the number of images already checked:
"You need another -823 images to reach the rank of a Chief inspector."

Also, you may want to capitalize "Inspector" (and I'm not sure if it should be "rank of a" or just "rank of").

e.g. I got an exposure where the seeing was bad enough and the field was dense enough that everything was blended. It's not technically a failure in the sense that something went wrong with the processing, but it's an image that we should probably omit from our subsequent analyses.

So my proposal is that the failure problem should bring up a text box to indicate why the field is considered a failure.

By popular demand: To share or return to a specific exposure, it would be good if one could get a URL to send around or mechanism to bookmark the page.

Due to latency or twitching trigger finger I double click next. It would be useful to be able to go back to the previous image

Over-subtraction shows up often enough (at least 20% of the time), that it would be useful to have it's own space in the drop-down menu.

Don't need WCS positions, but, say, center-chip location would be nice to have.
It would suffice to have that coordinate in the FITS header.

It is sometimes difficult to figure out which CCD you are looking at on the FoV png. It would be nice to be able to either highlight the CCD of interest or show a map of the CCD numbering next to the FoV png. For example, showing an image like the one attached next to the FoV png would probably suffice (however, this mapping appears to be rotated relative to the FoV png).

• Peter's presets and arcsinh seem to be the same (not sure if that's intended)
• Sometimes scaling switches to linear even when arcsinh was selected initially

It wasn't initially obvious to me that Save was the way to move onto the next image when problems were marked. And I saw Bhuv hit Save for one of the problems and then start to try to mark another problem he noticed, even though it was now loading the next image (slowly with the internet here).

Also, I'm guessing that if you have marked problems and then press OK, it sort of resets all the problems that were set and calls the image OK, which is probably not what you want.

So I think it might be better to have the "Save" button take the place of the "OK" button when problems are set. (And still add the new "Clear" button that shows up then.) I think that would be more intuitive that this is how you move on to the next image after marking all problems. And it would prevent people from pressing OK after marking problems (without pressing clear that is).

This is probably hard, but:

Have a form a user can fill out a title and description, and this will appear in the pull down menu for problems; it would still get put into the db as "other" but this way the user doesn't have to type the same text over and over.

Zoom into the image or bigger images to make use of larger screens.

'tree rings' show up often enough (at least 10% of the time, more often than ghosts and cosmic rays), that it would be useful to have it's own space in the drop-down menu.

I've seen some cases where bad columns or CRs seemed only partially masked. This might well be how it is in the data, but it could also appear so because of downsampling of the mask. This is just to ask whether you make sure to display a downsampled super-pixel as masked whenever any part of it is masked in the original resolution images.

It would be helpful to have the last couple of problems you have marked show up in the pull down menu.

By Chris Davis: "Would it be possible to add a keyboard shortcut for toggling the mask? I find it useful sometimes to blink the mask."

More general, can we add key bindings to well-defined repetitive tasks?

It would be helpful to be able to clear single regions, or a single layer of marks --- instead of having to clear everything with the 'clear' button.

To keep the competition lively, it might be useful to have a leaderboard for each data release (e.g., SVA1, Y1A1, etc.). That way, new people can start on equal footing with each new data release. I don't know how multiple data releases are being implemented, so this may be impossible.

Either by specifying exposure and ccd separately or by speficying the combo name such as

DECam_00163606_38

replace "display options" with two small buttons that are for asinh and peters.

Use brief names "asinh" "peter"?

The loading spinner is shown only for the action of loading the image, but not for the rest of the server-client communication. Therefore, there can be (and often is) a gap between a user hitting the "next" button and the appearance of the spinner. Occasionally, users hit "next" again, which would apply to the next image if it had started loading by that time.

To avoid that confusion, show the spinner directly after "next" has been hit and at the initial loading of the page.

Would be helpful for the cursor to automatically be placed in the dialog box when we select 'other' or 'failure'

Could next image be cached while I inspect the current one since this might save time?

'vertical streaks' show up often enough (at least 10% of the time, more often than ghosts and cosmic rays), that it would be useful to have it's own space in the drop-down menu.

I've seen a number of artifacts that look like background subtraction problems. In particular, near the edges when there is a bright star close to the edge. But in general, I suggest adding "background subtraction errors" as a type of problem.

Risa pointed out that it would be also nice to be able to mark cool and/or interesting objects (strong lensing, merging galaxies, etc...), in addition to marking problems.

Since we're looking at the images anyway, it would be nice to be able to leverage that activity for scientifically interesting things as well.

Showing user with a problem and asking him to find and mark the given problem. The module has to be integrated with viewer itself.
User will be directed to this page after equal intervals, and is asked to ace a new set of problem categories (staring from the obvious to difficult ones).

Requirements:

1. To have a table for set of problems images and question categories.
2. List/Table of problem classes aced by User. (Add a Label- Problems Aced in user statistics)
3. Integration in Viewer

Maybe it needs to remind one to mark the artifact since I just realised I should have been marking all the artifacts since my number of reported images was low.

I would select the kind of artifact and then hit next. Yes, I am dumb. I marked the awesome objects.

i.e. mabe this is hard to trap. I sequesne was to select the the kind of artifact with the drop down and then hit next

Needs:

• (delayed) loading of login.js
• login modal from index.html
• redesign of index.html
• hiding/excluding user-menu and getMyData when user is not logged in

The eyeball squad has checked ~3000 exposures. Their approach is favorable for FoV-sized artifacts such as ghosts or scattered light, which are harder to diagnose on chip-size images. We could show the report of the eyeball squad together with the image from #19 .

It'll require a new database table with the eyeball squad data parsed properly. One issue is the conversion of chip labels ("S31") to ccd numbers. Other may arise, so this requires some hand-holding.

On the client side, we could have a toolbox with the link to the DESDM fits file, the FoV-size png image, and the eyeball-squad report.

It will be nice if one can go back to the previous image. It helps to remove accidental submissions

If the scaling panel is outside the image panel it will be easier to find problems in the image by changing the scaling option.

The "display options" button is annoyingly far away from the fine and problems -> streamline to have more images checked in given time

The basic statistics require a sweep over all reported problem cases. This is currently very slow (apparently fast only when the result is cached on the server), so that the page appears empty from ~30 seconds.

A index on the problem column in the db should alleviate that.

It would be useful for hitting 'enter' to apply to the 'done' button.

... should be another named problem.

it would be useful to have the url to original desdm image since in some cases I
would like to load FITS image into ds9 or local software

The image is rotated by 180 degrees with respect to the input images. This becomes and issue when someone uses the API to get coordinates for the artifacts.

We can either rotate the FITS image or do the rotation in the viewer. If not prohibitive performance-wise, the browser solution is preferred.

However, once the rotation is implemented, the coordinates in the database need to be converted, too.

We made some configuration changes on the server at BNL. The server now supports https and regular http access. The config file has changed. Make sure none of this caused problems for the exposure checker.

add a link to the full exposure images from DESDM

The tutorial needs to show what kind of things we want to find in the images, with one good example for each of the data flaws we're after. Also, some of the experts should provide a short explanation about the origin of the effect, and possible what DESDM already does about it.

as part of a recent commit, some functionality has been changed so that both of the button in index.html are now disfunctional

Problems reporting may benefit from further explanation. For example, occasionally a cosmic ray mask is applied without a visible cosmic ray streak. It may be nice for the scanner to add notes to a given image. The "Notes" button could have essentially the same behavior as "Other" but without marking a specific location on the image.