Field Science issueshttps://code.cs.earlham.edu/groups/field-science/-/issues2019-06-16T13:30:23-04:00https://code.cs.earlham.edu/field-science/FieldDay/-/issues/1Re-Read Button2019-06-16T13:30:23-04:00Craig EarleyRe-Read ButtonIt would be nice to have a re-read button next to the stream button in 'Take a Sample'.It would be nice to have a re-read button next to the stream button in 'Take a Sample'.First Field Day FridayCraig EarleyCraig Earleyhttps://code.cs.earlham.edu/field-science/fjord-cam/-/issues/2Image quality comparison2023-02-15T14:39:12-05:00Porter LibbyImage quality comparisonFOV, fstop, exposure may all make a difference for this project.FOV, fstop, exposure may all make a difference for this project.https://code.cs.earlham.edu/field-science/fjord-cam/-/issues/1Add higher res image from GoPro2023-02-15T14:37:31-05:00Porter LibbyAdd higher res image from GoProGoPro has photo resolution options. The images I have been capturing are 5MP, but I think it can scale up to 11MPw.GoPro has photo resolution options. The images I have been capturing are 5MP, but I think it can scale up to 11MPw.Porter LibbyPorter Libbyhttps://code.cs.earlham.edu/field-science/datavis/-/issues/23Import CSV without spotname field, use id or spotid in place of2022-05-31T12:47:30-04:00Porter LibbyImport CSV without spotname field, use id or spotid in place ofhttps://code.cs.earlham.edu/field-science/images/-/issues/11Remove API key from web-image-display/imageThumbnails.php2021-12-08T08:49:46-05:00Porter LibbyRemove API key from web-image-display/imageThumbnails.phpShould be included in a config file or envShould be included in a config file or envhttps://code.cs.earlham.edu/field-science/FieldDay/-/issues/47Rearrange and rephrase UI buttons2021-04-03T10:12:40-04:00Craig EarleyRearrange and rephrase UI buttons[See this photo of the new layout (the whiteboard text on the right)](/uploads/0e2744b4a152f3d4bba5543fe14ea803/field-day-ui-revise.jpg)[See this photo of the new layout (the whiteboard text on the right)](/uploads/0e2744b4a152f3d4bba5543fe14ea803/field-day-ui-revise.jpg)https://code.cs.earlham.edu/field-science/FieldDay/-/issues/46Crash on tapping the bench sample picture button2021-03-10T10:27:00-05:00Craig EarleyCrash on tapping the bench sample picture buttonText of logcat message will be in the comments.Text of logcat message will be in the comments.https://code.cs.earlham.edu/field-science/FieldDay/-/issues/45Fix the way we do uploads2021-02-08T11:10:28-05:00Craig EarleyFix the way we do uploadsGathering field data works, but we get a lot of buggy behavior around uploads.
After an upload of, say, X streaming and Y reading rows, we still see X and Y as the local database status. Our understanding should be that, once we’ve uplo...Gathering field data works, but we get a lot of buggy behavior around uploads.
After an upload of, say, X streaming and Y reading rows, we still see X and Y as the local database status. Our understanding should be that, once we’ve uploaded them to the central database, those rows are no longer "local" to the device only.
There are a few possible solutions, and we should discuss them:
1. Completely re-do database setup after each upload - we might then relabel “Upload” as “Upload and sync”. I mildly favor this approach over the others.
2. Auto-sync everything whenever we have Internet.
2. [I think this approach is rejected.] Re-sync the uploads database only. This presents challenges for consistency: on initial setup, we have a complete clone of the subset of the database that’s relevant to our chosen trip. If we merely bring back the timestamp, our uploads would be consistent but nothing else.https://code.cs.earlham.edu/field-science/FieldDay/-/issues/44Discussion and notes: user interface and feature ideas2021-02-08T11:05:33-05:00Craig EarleyDiscussion and notes: user interface and feature ideasWe need to sort these. Many of these bullet points could become issues, but I am mainly using this is a heap where I can dump the information.
Some of our ideas. Some have issues associated with them already.
1. Move the sampling stuff...We need to sort these. Many of these bullet points could become issues, but I am mainly using this is a heap where I can dump the information.
Some of our ideas. Some have issues associated with them already.
1. Move the sampling stuff to the front screen
2. Scrolling
3. Brighter buttons, more muted backgrounds (including gray rather than bright colors)
4. Bigger buttons
5. Less on any one screen? So split DB actions into multiple screens, for example
6. Linear user flow: database -> platform -> sample (or platform -> sample -> DB)
7. Gestures?
8. Rotation #33
Other stuff
dark mode?
```
setContentView(R.layout.activity_database_actions);
View someView = findViewById(R.id.databaseStatus);
// Find the root view
View root = someView.getRootView();
// Set the color
root.setBackground(getDrawable(R.drawable.background_dark));
```
Navigation (unordered)
* Get a toolbar that can take you to the things you rarely need:
* Settings
* About
* Sensors are the big-ticket items, they get most of the real estate under that
* Database setup and lab notebook are beneath them
* Other
* NavigationUI
* ActionBar
more ideas
* automated unit tests?
* revise data model/re-architect # some notes: two columns: headstream, varchar(5) - sampleunitid, integer (taking the place of spot or stream id)
* license
* take picture of spot, where a spot’s image includes the 3 flags where we’re digging - picture may also include surrounding area, want to correlate images to the data from microbial sampling
* bad idea to have CREATE statements in code a la ReadingsDatabase?
* 2. Fieldday_Streaming_GIS table, with geopoint, is not used
* Postgres fieldday_streaming_gis table
* We should add the geopoint to the fieldday_streaming table
* compute geopoint based on lat and long columns
* mutually_exclusive_group?
* document our testing
* Test elevation streaming
* Leave, walk downstairs, go to the rock, come back
* Or, leave, go to the first crack in the sidewalk at the 4-way stop at public safety where there will be the top of a 2x2 with a nail
* quality control
* rotations
* no sector is displayed but the device will still stream when the button is pressed
* maybe a display problem not a data problem? streaming data appears to be collected
* also the stream button doesn’t blink
* but we get a weird runaway streaming problem where I can’t seem to stop the streaming after a rotation
* Field Day crashes on erasing local database if you have already done so
* Can’t select a sector with the default site, have to change it to get the sector dropdown active
* Number of values each sensor returns
* some return 1,2,3, etc. values
* we don’t do a good job of detecting the number of values in-place
* UX questions
* What do people do? Is there an order?
* Display aggregates - what kinds? count of reads/streams? mean/median/mode/range? lat/long/times start/stop? can there be a map?
* Global settings, or settings changed rarely (e.g. databases)?
* What devices? Is this mainly a tablet app, phone app, or both? (I think both)
* Documentation: "As previously mentioned, the map() function uses integer math. So fractions might get suppressed due to this. For example, fractions like 3/2, 4/3, 5/4 will all be returned as 1 from the map() function, despite their different actual values. So if your project requires precise calculations (e.g. voltage accurate to 3 decimal places), please consider avoiding map() and implementing the calculations manually in your code yourself."
* [Storage Access Framework](https://commonsware.com/blog/2019/06/07/death-external-storage-end-saga.html)https://code.cs.earlham.edu/field-science/images/-/issues/10Run a programmatic quality check on 3D assemblies2020-10-13T10:13:03-04:00Craig EarleyRun a programmatic quality check on 3D assembliesWe have two possible approaches to quality checking 3D (and maybe 2D) assemblies:
* Sobel edge detection
* tricks in ImageMagick
Edge detection is a more well-defined place to begin, so let's start there.We have two possible approaches to quality checking 3D (and maybe 2D) assemblies:
* Sobel edge detection
* tricks in ImageMagick
Edge detection is a more well-defined place to begin, so let's start there.https://code.cs.earlham.edu/field-science/FieldDay/-/issues/43Test Slack integration2020-04-29T10:07:36-04:00Craig EarleyTest Slack integrationThis issue will test Slack integration. It will be closed immediately.This issue will test Slack integration. It will be closed immediately.https://code.cs.earlham.edu/field-science/FieldDay/-/issues/42Database upload should check for sample spot images and upload those too2020-02-11T09:12:51-05:00Craig EarleyDatabase upload should check for sample spot images and upload those tooDatabase upload should check for sample spot images and upload those too, possibly via Postgres to an external file?Database upload should check for sample spot images and upload those too, possibly via Postgres to an external file?https://code.cs.earlham.edu/field-science/FieldDay/-/issues/41Sample spot image file names should be auto-generated, not user entered2020-02-11T09:11:17-05:00Craig EarleySample spot image file names should be auto-generated, not user enteredSample spot image file names should be auto-generated, not user entered, i.e. site-sector-spot-type-date.pngSample spot image file names should be auto-generated, not user entered, i.e. site-sector-spot-type-date.pnghttps://code.cs.earlham.edu/field-science/FieldDay/-/issues/40Develop process for retrieving images from device2020-02-08T09:57:58-05:00Craig EarleyDevelop process for retrieving images from deviceWe should have a process for retrieving sample spot images in Field Day at the same time as a user uploads data or clears local storage. This includes documentation.We should have a process for retrieving sample spot images in Field Day at the same time as a user uploads data or clears local storage. This includes documentation.https://code.cs.earlham.edu/field-science/FieldDay/-/issues/39Integrate ground control points into Field Day's location data2020-01-24T14:48:48-05:00Craig EarleyIntegrate ground control points into Field Day's location dataThis might be in the form of scanning a QR code, detecting it based on GPS location, or something else.This might be in the form of scanning a QR code, detecting it based on GPS location, or something else.https://code.cs.earlham.edu/field-science/FieldDay/-/issues/38Add a trip-site-sector-spot on the fly2020-01-16T13:47:15-05:00Craig EarleyAdd a trip-site-sector-spot on the flyI could imagine a situation where we're in the field and discover we want to take a Field Day reading somewhere that doesn't match an existing trip-site-sector-spot.
Right now, I think we have to do that on the server side. It may be us...I could imagine a situation where we're in the field and discover we want to take a Field Day reading somewhere that doesn't match an existing trip-site-sector-spot.
Right now, I think we have to do that on the server side. It may be useful to do it in the field just like we do everything else.
One possible approach among many: "Add a site", for example, could be added to the site dropdown. (Adding a trip could be trickier.)https://code.cs.earlham.edu/field-science/FieldDay/-/issues/37Consolidate all documentation for how to use Field Day2020-09-30T09:34:34-04:00Craig EarleyConsolidate all documentation for how to use Field DayWe have several documents to the effect of "how to use Field Day". That can get confusing. We should centralize those here - the README for general users, and maybe a CONTRIBUTING page for developer notes that are appropriate for public ...We have several documents to the effect of "how to use Field Day". That can get confusing. We should centralize those here - the README for general users, and maybe a CONTRIBUTING page for developer notes that are appropriate for public visibility - to simplify our lives.https://code.cs.earlham.edu/field-science/FieldDay/-/issues/36Aggregate the magnetometer data2019-11-19T12:40:25-05:00Craig EarleyAggregate the magnetometer dataThis topic is too broad for a single issue, but I wanted to flag it for discussion and initial script development.
We've talked for a few years about using the magnetometer data that Field Day gathers from the OS as part of the internal...This topic is too broad for a single issue, but I wanted to flag it for discussion and initial script development.
We've talked for a few years about using the magnetometer data that Field Day gathers from the OS as part of the internal sensors function. We should start doing this, as it has implications for several workflows.https://code.cs.earlham.edu/field-science/FieldDay/-/issues/35Rename and add information to the Protocols feature in Notebook2021-04-03T10:13:50-04:00Craig EarleyRename and add information to the Protocols feature in NotebookThere's a collection of features called "Notebook" in Field Day, and it includes Google Drive, "Note Pad", and "Protocols". Currently, "Note Pad" has minimal functionality and "Protocols" has none (for historic reasons that aren't releva...There's a collection of features called "Notebook" in Field Day, and it includes Google Drive, "Note Pad", and "Protocols". Currently, "Note Pad" has minimal functionality and "Protocols" has none (for historic reasons that aren't relevant to the current configuration). This issue is about Protocols.
I propose we add buttons pointing to a few pieces of read-only content to the Protocols section:
- a frequently-asked-questions page
- troubleshooting common problems
- our glossary of terms (currently in Drive)
- maybe move the About and Settings buttons here, off the valuable main screen
Since this strays from some strict lab definition of "protocols", consider renaming it as well.https://code.cs.earlham.edu/field-science/FieldDay/-/issues/34No indication when the GPS signal is lost2019-09-21T10:24:05-04:00Tamara BlagojevicNo indication when the GPS signal is lostThere should be some kind of indication when the GPS signal is lost so we know that the drone is not collecting dataThere should be some kind of indication when the GPS signal is lost so we know that the drone is not collecting dataTamara BlagojevicTamara Blagojevic