Git Product home page Git Product logo

farmdata2-190wid-s23's People

Contributors

96radhikajadhav avatar amelia291 avatar anisha-art avatar batese2001 avatar boosungkim avatar braughtg avatar braughtstu avatar ezinneanne avatar futzmonitor avatar goldberl avatar hoad211 avatar irissc avatar jingyumarcellee avatar johnmaccormick avatar josieecook avatar kvaithin avatar miyu386 avatar mollerup23 avatar msaadm avatar savidbasnyat avatar shes-dev avatar skalakm avatar vuphuongha avatar walnuthanhan avatar won369369 avatar

Stargazers

 avatar

Watchers

 avatar

farmdata2-190wid-s23's Issues

Seeding Report: Invalid Results in Tray Seeding Summary

Description:
From Jan 1, 2019, to Jan 15, 2020, in the Seeding Report of BarnKit, the Tray Seeding Summary table displays NaN (Not a Number) for two fields "Total Number of Tray Seeds Planted" and "Average Seeds Planted per Hour".

Steps to Reproduce Bug:

  1. Visit the Seeding Report sub-tab of the BarnKit tab.
  2. Set Dates from 01/01/2019 to 01/15/2020.
  3. Click Generate Report.
  4. Scroll to the bottom of the page to view Tray Seeding Summary.

Observed Result:
Dates:
image

Output:
It shows NaN (Not a Number) in both fields "Total Number of Tray Seeds Planted" and "Average Seeds Planted per Hour".
image

Desired Result:
The system will generate specific numbers for every field in the Summary Table.
For example, I set the dates ranging from 01/01/2020 to 01/15/2021 and the table contains only proper values.
Output:
image

Update README with links

The README.md file should be updated with links to the appropriate resources.
In additions, logos and images for GPL3, CC, farmOS, NPFI, NSF, GNOME might be added as well.


Issue by braughtg
Saturday Oct 10, 2020 at 19:14 GMT
Originally opened as DickinsonCollege#16

Seeding Report: Incorrect Date ordering

Description

In the seeding report the results are sometimes not correctly order by date. The results are ordered by date for each type of seeding separately, when the two groups should not be split.

Directions

  • Open a seeding report from 5/1/2020 to 4/5/2023
  • Scroll to the first appearance of the date 2020-07-10
  • Following this date the next row is seeds planted 2 months earlier

Observed Output

Screen Shot 2023-04-05 at 9 29 37 AM

Expected Output

The rows should be ordered by date regardless of the seeding process.

Seeding Input: default unit is bed

The default for the feet unit (inside the Direct Seeding inputs) should be bed. It defaults to blank right now.

defaultToBed

To test this go to the Seedings Input subtab under FieldKit tab, which is on the home page.

The code can be found by going to farmdata2_modules/fd2_tabs/fd2_field_kit/seedingInput.html file.


Issue by IrisSC
Friday Jul 23, 2021 at 20:17 GMT
Originally opened as DickinsonCollege#271

Add links to the Workflow section of CONTRIBUTING.md

The primary steps of the GitFlow workflow are outlined here. They could be augmented with links for each of the steps so that they would be useful to relative new comers to FOSS. GitHub provides useful help pages for each of these steps that can be found and linked.


Issue by braughtg
Monday Nov 16, 2020 at 16:52 GMT
Originally opened as DickinsonCollege#34

Seeding Report: Allows Invalid Inputs

Description: Users are able to enter invalid inputs such as negative values into the Seeding Input Log of FieldKit

Steps to replicate this problem:

  1. Log into FarmData2 with the correct user credentials
  2. Click on the tab FieldKit and then click on Seeding Input
  3. Under the label "Labor" fill in a negative value for workers and time
  4. Click submit and Generate Report

Observed Output

image

Desired Output

There should not be a bottom error option available to click to generate a negative value.


Issue by anlai46
Thursday Dec 16, 2021 at 08:52 GMT
Originally opened as DickinsonCollege#344

Seeding Report: Invalid output 'NAN'

Description:

When given certain date ranges, the sections “Total Number of Tray Seeds Planted” and “Average Seeds Planted per Hour” of the Seeding Report Summary Table give values 'NAN' (Not A Number) instead of normal values.

Steps to replicate:

Log into FarmData2
Click Seeding Report at BarnKit
Set the date range: Start Date is 04/01/2019 and End Date is 06/01/2019
Click Generate Report

Output:
Screenshot 2023-04-12 at 3 49 45 PM

Desired result:
The sections “Total Number of Tray Seeds Planted” and “Average Seeds Planted per Hour” of the Seeding Report Summary Table should output proper numerical values instead of 'NAN'

Seeding Report: no logs in table, display a message

If there are no logs in the table then the filters, table, and summaries do not show up. The page where they should be is just blank. Instead we want there to be a message saying “There are no logs in the time range you have selected. Please select new dates.”

There are two scenarios when the filters, table, and summaries disappear. First is when there are no logs within the date range, the second is when the user deletes all the logs in the date range. This is likely due to there being no logs in the array seedingLogs.

To test this go to the Seedings Report subtab under BarnKit tab, which is on the home page.

NoLogsNeedMessageIssue


Issue by IrisSC
Friday Jul 23, 2021 at 17:56 GMT
Originally opened as DickinsonCollege#258

Tray Seeding Summary Table showing NaN in Seeding Report

Description:
In the Seeding Report, under the tab “BarnKit,” the Tray Seeding Summary table shows 4 statistics, “Total Number of Tray Seeds Planted,” “Total Number of Trays,” “Total Hours Worked,” and “Average Seeds Planted per Hour.” When putting in a particular data range, “Total Number of Tray Seeds Planted” and “Average Seeds Planted per Hour” are reported as NaN instead of their exact values. These incorrect values are dependent on the date.

Replication of the problem:

  1. Log into FarmData2 with your proper login credentials
  2. Go to the BarnKit tab and press “Seeding Report”
  3. Set Dates:
    Start Date: 06/01/2019
    End Date: 07/01/2019

Picture1

  1. Set Filters:
    Type of Seeding: Tray Seedings
    Crop: All
    Area: All

Picture2

  1. Scroll down to the “Tray Seeding Summary” at the bottom of the Seeding Report to see the issue

Observed Result:
Picture3

Expected result:
The “Total Number of Tray Seeds Planted” and the “Average Seeds Planted per Hour” should not have output NaN as the value. It should report the exact values, in decimal format, for each statistic regardless of the date inputted.

Seeding Report: Inconsistent Date Ordering

Description

The seeding report groups its reports intro Direct Seedings and Tray Seedins and then sorts by date rather than only sorting by date

Steps to replicate issue

  • go to Seeding Report by clicking on the BarnKit tab and the Seeding Report tab
  • under Set Dates enter 05/05/2020 as the Start Date and 07/11/2020 as the End Date
  • click on the Generate Report button
  • then scroll down to the first item that says Tray Seedings under the Tray/Direct column

Observed Output

image

Desired Output

All of the items should be sorted by date and shouldn't be split into two seperate groups.

Cypress.json: Fix Indentation Error

How to Produce this Bug

  1. Visit the file either on GitHub here or on your editor of choice.
  2. Navigate your cursor down to "testFiles" on line 13 which has one extra space.
image
Red highlight indicates the existence of an extra space.

Steps for Solving this Bug

  1. Fork the repo and edit the file either within GitHub or within your editor of choice.
  2. Remove the extra space so that the line is in-line with the line above. The final product would look something like this.
image
Notice: Red highlight is gone because the extra space has been deleted.

Issue by FutzMonitor
Tuesday Jun 28, 2022 at 20:18 GMT
Originally opened as DickinsonCollege#507

Barn Kit Sub-Tab Ordering

The "Info" subtab on the Barn Kit tab should appear on the left. The Seeding Report sub-tab should appear to the right. This ordering is controlled by the weights assigned in the farmdata2_modules/fd2_tabs/fd2_barn_kit.module file.


Issue by braughtg
Wednesday Sep 22, 2021 at 12:19 GMT
Originally opened as DickinsonCollege#283

Seeding Report: Incorrect Values in Tray Seeding Table

Description

When certain dates are entered into the Seeding Report, the Tray Seeding Table displays "NaN" instead of numerical values for "Total Number of Tray Seeds Planted" and "Average Seeds Planted per Hour".

Replicate the Bug

  1. Go to BarnKit and select the Seeding Report Tab
  2. Enter 01/01/2019 as the Start Date, and enter 07/17/2019 as the End Date
  3. Generate the Seeding Report
  4. In the Filters field, click on the Type of Seeding dropdown menu and select Tray Seedings
  5. Scroll down to the bottom of the page to observe the bug in the Tray Seeding Summary table

Expected Result

The expected result should be the value in the "Total Number of Tray Seeds Planted" and "Average Seeds Planted per Hour" that is the correct calculation of the selected data.
Correct Answer

  • These values are the result of putting 01/01/2019 into the Start Date and 03/30/2019 into the End Date

Observed Result

The observed result is "NaN" is displayed in the "Total Number of Tray Seeds Planted" and "Average Seeds Planted per Hour" instead of a numerical value.
TraySeedingNaN

Seeding Report: data not ordered by date correctly

The data in the main table found within the BarnKit's Seeding Report page is not ordered by date correctly, when it should be. An example is as follows:

image

As observed, the table has data from July of 2020 preceding data from June of 2020, when the expected result should be the other way around (ordered by youngest dates to oldest or June then July in this context).

The error can be reproduced by entering the date range as 06/26/2020 to 07/10/2020.

Seeding Report Editing Issues/Bugs/Concerns

Which columns in the seeding report should be editable and when?

  • It seems to make sense that some columns should be editable and some may not be.
    • For example, you can edit hours but not the type of seeding.
    • When a column that needs to be changed (e.g. type of seeding) is not editable the solution is to delete the log and recreate it.
  • Seems like some things should be able to be edited or deleted only under certain conditions.
    • What happens if a transplanting or harvesting log already exists that is associated with the seeding?
    • This needs to be researched. Perhaps if the planting is changed then everything will be alright?
    • Note however that the crop_tid field added to the seeding logs to make it unnecessary to fetch the plantings will also need to be updated if the crop is edited.
  • When editing the location of a seeding the options should be consistent with the seeding type.
    • Only greenhouses for tray seedings and only field or bed locations for direct seedings (as in the input form)
  • When editing fields that are constrained (e.g. hours or workers) the edit field should be a RegexInputComponent with an appropriate regular expression to prevent invalid inputs.

Issue by braughtg
Tuesday Jun 07, 2022 at 19:37 GMT
Originally opened as DickinsonCollege#466

Seeding Input: required input fields are marked

All inputs, besides comments, are required. The submit button will be disabled until they are filled out. The inputs are not marked, so a user could find this confusing. Mark all the required inputs with a little red asterisk next to each. Put a little note at the bottom of the page before the submit that all inputs with the red asterisk are required(line it up with input boxes).

To test this go to the Seedings Input subtab under FieldKit tab, which is on the home page.

The code can be found by going to farmdata2_modules/fd2_tabs/fd2_field_kit/seedingInput.html file.


Issue by IrisSC
Friday Jul 23, 2021 at 19:34 GMT
Originally opened as DickinsonCollege#264

Seeding Report: Incorrect Output Sorting by Date

The program produces incorrectly sorted output by date within a specific date range.

Proof1

To reproduce:

  • Go to BarnKit -> Seeding Report
  • Select Start Date: 08/29/2019
  • Select End Date: 03/14/2020
  • Generate Report
  • Scroll the report down until the date 03/12/2020

Expected Output:

The program successfully sorts the output by the date indicated in the date range (scrolling the report down produces the most recent dates)

Observed Output:

The program sorts the output incorrectly, placing older dates after the more recent dates, and disturbing the natural order of the output.

Note: The output produced only occurs within specific date ranges such as the one indicated above.

Seeding Report: Ordered by Tray/Direct Column Rather Than by Date

Description: When generating a Seeding Report between certain time spans, the table organizes itself by the Tray/Direct column instead of the Date column.

Directions To Replicate Bug:

  1. Open a version of FarmData2 running on the Sample Dataset.
  2. Navigate to BarnKit, Seeding Report.
  3. Select dates from 03/10/2020 to 04/07/2020 and generate report.
  4. Scroll through the report until entries in the Tray/Direct column switch from Direct Seeding to Tray Seeding.

Screen Shot 2023-04-03 at 6 45 35 PM

Expected result:

This bug can be considered fixed when the entries in the table appear sorted by date, from oldest to newest, within any time range.

Observed Result:

The Direct Seeding entries appear first and are ordered from oldest to newest. Then the Tray Seeding entries are listed, oldest to newest. Since the newest Direct Seeding is newer than the oldest Tray Seeding, the table is out of order.

Discussion:

The date range 02/15/2019 to 04/05/2019 will also produce this error. These were the shortest ranges that I found. If you shorten this range or the previous range by 1 day then the table will be formatted correctly. The error will still appear if either of these ranges are expanded.

Seeding Report: NaN in Tray Seeding Summary

Description: In some date ranges, the "Total Number of Tray Seeds Planted" and "Average Seeds Planted per Hour" is shown as "NaN" rather than a proper value.

Directions to Replicate:

  1. Select the BarnKit tab and click on the Seeding Report sub-tab.
  2. Choose 01/01/2019 as the start date and 05/13/2019 as the end date.

image

  1. Generate the seeding report.
  2. Scroll down to the Tray Seeding Summary.

Expected Result: The "Total Number of Tray Seeds Planted" and "Average Seeds Planted per Hour" should give a numerical value based on the selected data.

image

Observed Result: In the date range given above, the "Total Number of Tray Seeds Planted" and "Average Seeds Planted per Hour" are displayed as "NaN."

image

Review Language for Inclusivity

Review FarmData2 documents with respect to inclusivity of language. This issue has been created proactively rather than reactively. Pull requests with language revisions for review are welcome.

See "Google’s initiative for more inclusive language in open source projects" for some ideas of what to look for and revisions that might be made as necessary:


Issue by braughtg
Tuesday Nov 10, 2020 at 20:59 GMT
Originally opened as DickinsonCollege#32

Seeding Report: "NaN"/Seeding report issue for years 2018-2020

Seeding Report Issue:

(Certain data ranges cause volatility amongst outcome)

Steps to Replicate:

  1. Visit Seeding Report sub-tab of the BarnKit tab.
  2. Select Start Date: 01/01/2018
  3. Select End Date: 01/01/2020
  4. Select Type of Seeding: Tray Seedings
  5. Generate Report

OG Dates

Expected Result:
The main table at the bottom of the Seeding Report should have actual numbers/integers for ALL values. None of the values should have a value of "NaN".

Desired Outcome

Observed Result:
When the data is in a specific range (I found that data from 2018-2020) create this problem much more often than data before 2018. The Total Number of Tray Seeds Planted has a value of "NaN", as well as the Average Seeds Planted per Hour.

OG outcome

I assume that there is a problem with data that is from previous years causing this bug because when I focused on timeframes in later years, the bug did not occur.

BarnKit- Seeding report: Limit Dates to Existing Data?

Description: Users could enter invalid input data for checking Seeding Report in BarnKit tab

Steps to replicate the error:

  1. Log in using your account.
  2. Go to the BarnKit tab and click on the Seeding report at the left corner of the window.
  3. Enter some weird value for the year and don't do anything more!

This is an image
When it comes to this page, there is no alerts for entering such non-sense dates.

Only shows up error when people click on "Generate Report" button.

Oberseved output
This is an image

Desired output: Users should not be allowed to choose inputs for year that is earlier than the creation of the farm or laster than today's date.


Issue by AdiaWu
Saturday Dec 18, 2021 at 08:11 GMT
Originally opened as DickinsonCollege#347

Seeding Report: NaN values in Tray Seeding Summary

In the Tray Seeding Summary Table, the "Total Number of Tray Seeds Planted" and "Average Seed Planted per Hour" will report NaN values depending on the Start Date.

Steps to replicate:

  1. Visit the Seeding Report sub-unit of the BarnKit tab.
  2. Under Set Dates, select 13/06/2019 as the Start Date and choose any End Date to generate reports.

Observed Results
It seems that selecting any date prior to 14/06/2019 as the Start Date will cause the "Total Number of Tray Seeds Planted" and "Average Seed Planted per Hour" to report NaN instead of actual values.

Screen Shot 2023-04-04 at 11 50 30 PM

Desired Results
The "Total Number of Tray Seeds Planted" and "Average Seed Planted per Hour" should report proper values regardless of the start date.

Seeding Report: Not all reports are in order based on date

Description: When generating a Seeding Report between specific time spans, the table does not always order the reports correctly by date,
Screen Shot 2023-04-04 at 4 20 41 PM
Directions To Replicate Bug:
-Open FarmData2 and enter your credentials.
-Navigate to BarnKit and click Seeding Report.
-Select dates from 08/14/2022 to 03/27/2023.
Scroll through the report until entries until you see that the dates are indeed not in the correct order

Expected result:
-This bug will be fixed when the entries in the table always appear sorted by date, from oldest to newest.

Observed Result:
-The seeding reports are not always listed from oldest to newest, specifically when switching from 2022 to 2023.

Update required field message in seeding inputs

The comment at the bottom of the form states "* All inputs with astrix are required and must be filled before submitting the report" This should be rephrased to be: "* required field."

The code for the seeding input log is found in farmdata2_modules/fd2_tabs/fd2_field_kit/seedingInput.html


Issue by braughtg
Monday Oct 04, 2021 at 14:24 GMT
Originally opened as DickinsonCollege#287

Seeding Report: Improper Date Sorting in Table

The Seeding Report sorts information by date in two sections - Direct Feeding and Tray Seedings - instead of sorting all information by date alone.

Steps to Replicate:

  • Visit the Seeding Report sub-tab of the BarnKit tab
  • Use 5/1/2020 as the start date and 5/26/2020 as the end date
  • Generate Report

Observed Result:
The planting for Sweet Potatoes (Direct Seeding) on 5/26/2020 comes before the planting for Cucumbers on 5/6/2020

image

Desired Behavior:
The table should be sorted entirely by date, regardless of seeding type.

Seeding Report: Main table data values unsorted

On the seeding report located under the BarnKit tab, there appear to be incorrectly sorted date values in the date range 06/01/2020 to 07/04/2020.

To recreate this bug

  1. Click on the BarnKit Tab
  2. Select the Seeding Report button
  3. Enter 06/01/2020 as the start date and 07/04/2020 as the end date
  4. Scroll until you see the date value equal to 2020-06-30
  5. You should be able to then see the date values equal to 2020-06-05 succeeding 2020-06-30

Observed output:
image

Desired output:
It should correctly sort date values for all date ranges

Hide Seeding Report Summary Tables While Loading

The summary tables that appear at the bottom of the Seeding Report should appear only after all of the data has been loaded. So while the data is loading the spinner should be the last element on the page. Once the data is loaded the spinner should disappear (as it currently does) and the summary table or tables should appear (related to DickinsonCollege#258 and DickinsonCollege#259). This modification should also include Cypress tests for the desired behavior.


Issue by braughtg
Wednesday Sep 22, 2021 at 12:34 GMT
Originally opened as DickinsonCollege#284

Seeding Input Erases Selected Area

On the Seeding Input form on the FieldKit tab, if the Area selected does not match the type of seeding that is chosen the Area will be cleared.

Steps to replicate:

  1. Visit the Seeding Input sub-tab of the FieldKit tab.
  2. Choose the CHUAU greenhouse as the Area for the seeding.
  3. Click the Direct Seeding radio button.

image

Similarly, when the seeding type is changed from Direct Seeding to Tray Seeding or vice versa then the Area chosen for the seeding is erased.

Steps to replicate:
4. Continuing from the prior steps...
5. Choose the ALF field as the Area for the seeding.
6. Click the Tray Seeding radio button.

image

Discussion

This behavior makes sense in that it ensures that Direct Seedings can only occur in fields while Tray Seedings can only occur in greenhouses. However, the behavior is confusing for two reasons:

  • Initially the dropdown contains all fields and all greenhouses making it seem like any are a valid choice for either type of seeding.
  • Changing from Tray to Direct Seeding or vice versa clears the prior choice of Area, which the user may not notice.

Desired Behavior

The desired behavior is for the Area dropdown to appear in the Tray Seeding or Direct Seeding portion of the form rather than in the Data (top) section of the form. This addresses both of the reasons for confusion outlined above:

  • The dropdown will not initially be visible. Once a Tray Seeding or a Direct Seeding is chosen, the dropdown will contain only the valid choices for Area.
  • Changing from Tray to Direct Seeding will still clear the Area drop down. However, because it is now contained in the part of the UI that is altered by the change of seeding type it will be apparent to the user that a new Area selection must be made.

This issue replaces DickinsonCollege#300.


Issue by braughtg
Wednesday Dec 08, 2021 at 17:27 GMT
Originally opened as DickinsonCollege#322

Seeding Report: date not sorted correctly

On the Seeding Report form on the BarnKit tab, for some date range such as from 5/11/2020 to 7/11/2020, the data in the main table is not sorted correctly based on date.

Steps to replicate:

  1. Click on the BarnKit tab
  2. Click on the Seeding Report sub-tab
  3. Set start and end dates to be 5/11/2020 and 7/11/2020 respectively
  4. Click on the Generate Report button

generate report

Observed Output:

image

Desired Output:

  • All the data generated should be sorted correctly by date.
  • It should work for any date range.

Seedings Report: delete total row/bed planted

The Direct Seeding Summary table that appears at the bottom of a Seeding Report contains a line for Total Row/Bed Planted. This metric not useful for farmers and clutters up the summary. Currently the summary table includes the Total Row/Bed Planted line which should be deleted:

image

To test this:

  1. Go to the Seeding Report subtab under the BarnKit tab
  2. Enter a start and end date for a report (any date window with direct seedings will be sufficient)
  3. Generate the report
  4. Examine the Direct Seeding Summary table at the bottom of the page.

The desired result will be similar to the following, where the Total Row/Bed Planted line has been removed:
image


Issue by IrisSC
Friday Jul 23, 2021 at 18:50 GMT
Originally opened as DickinsonCollege#260

Tray Seeding Summary report: incorrect result (NaN)

Description: From Jan 1, 2019 to July 15, 2020, the Tray Seeding Summary table displays invalid result (NaN) for both "Total Number of Tray Seeds Planted" and "Average Seeds Planted per Hour".

Direction:

  • Go to FarmData website.
  • Click on Barnkit.
  • Choose Seeding report.
  • Choose start date at Jan 1, 2019 and end date at July 15, 2020.
  • Click "Generate report"

Expected result:
Screen Shot 2023-04-04 at 21 57 30

A summary with valid result (positive number)

Result that we got right now:

Screen Shot 2023-04-04 at 21 59 26

Suggested solution:

  • Check if the method of calculating total and average.
  • Check the condition of input to avoid invalid number. @

Seeding Report: Table Dates Not Properly Sorted

Description: The main table in the Seeding Report is not properly sorted by the values in the date column within specific date range.

Steps to Replicate:

  1. Visit the Seeding Output sub-tab of the BarnKit tab.
  2. Select Start Date: 05/05/2020
  3. Select End Date: 05/18/2020
  4. Generate Report

Expected Result:
The main table in the Seeding Report is sorted by the values in the date column.

Observed Result:
When specific date range is selected, the main table in the Seeding Report appears to be sorted by Tray/Direct first, and then the values in the date column.
image

Seeding Report Page - Fix timing of report disappearing when new dates selected

The seeding report page hides everything but the date selection section when new dates are being chosen. Currently, the rest of the page disappears once the input has been changed and then clicked off of, instead of right after the initial click.
datechange

There are two possible solutions:

  • Change the page to hide the report right after the user does an initial click on the date inputs
  • Add a "Change Date Range" button that, when clicked, hides the rest of the page and allows the user to input new dates.

Issue by josieecook
Friday Jul 23, 2021 at 20:31 GMT
Originally opened as DickinsonCollege#274

Seeding Report: Invalid NaN values displayed in Tray Seeding Summary

Description: On the Seeding Report under the BarnKit tab the Tray Seeding Summary contains inaccurate Not a Number (NaN) values for "Total Number of Tray Seeds Planted" and "Average Seeds Planted per Hour" when the Start Date is between 01/01/2019-06/01/2019.

Directions to Replicate:

  1. Click on BarnKit tab and go to Seeding Report
  2. Enter a start date between 01/01/2019 and 06/01/2019
  3. Enter an end date between 07/01/2019 and present
  4. Generate Report
  5. Scroll down to view Tray Seeding Summary

Observed Result:
Here are my dates used to generate a report:
Screen Shot 2023-04-04 at 8 59 31 PM

Here is the result:
Screen Shot 2023-04-04 at 9 01 27 PM

Expected Result
Here are the dates used to generate a report with no errors:
Screen Shot 2023-04-04 at 9 06 00 PM

Here is the result:
Screen Shot 2023-04-04 at 9 06 29 PM

Tray Seeding Summary: Improper results (NaN)

Description: In Seeding Report, the Tray Seeding Summary may display improper results (NaN). Specifically, from January 1, 2019 to August 1, 2019, the total number of tray seeds planted and the average number of seeds planted per hour are both invalid.

Directions to Replicate the Bug:

  • Visit FarmData2
  • Click on BarnKit Tab then go to Seeding Report
  • Select any Date range from 01/01/2019 to 08/01/2019
    Click "Generate Report"

Expected result: The Tray Seeding Summary should display positive numbers.

Screen Shot 2023-04-04 at 8 07 56 PM

Observed result: "Total Number of Tray Seeds Planted" and "Average Seeds Planted per Hour" are reported as NaN values

Screen Shot 2023-04-04 at 8 16 49 PM

Seedings Report: message in Tray/Direct Summaries

A user may have all selected for Type of Seeding, but may have selected a crop or area that only has Tray or Direct Seedings. When this happens the other summary will show 0 or NaN (not a number), instead have that summary show a message: “There are no [Tray or Direct] Seedings in the options you have chosen.”

To test this go to the Seedings Report subtab under BarnKit tab, which is on the home page. Selected a date range, and try filtering different Areas and Crops.

An example is shown below:
NeedMessageTrayDirectSummaries

This issue is complete when the message appears in Tray and Direct seeding summaries, when there are no current logs in the respective summaries.


Issue by IrisSC
Friday Jul 23, 2021 at 18:33 GMT
Originally opened as DickinsonCollege#259

Seeding Report: NaN in Tray Seeding Summary

Description: Sometimes in the Tray Seeding Summary table at the bottom of a Seeding Report, the “Total Number of Tray Seeds Planted” and “Average Seeds Planted per Hour” are reported as NaN (Not a Number) instead of the proper values. The different behaviors seem to be dependent on the date range.

Steps to replicate this problem:

  1. Log into FarmData2 and choose Seeding Report at BarnKit
  2. Set Dates: Start Date is 05/28/2019 and End Date is 06/23/2019
  3. Click Generate Report
  4. Tray Seeding Summary table at the bottom of seeding report page

Observed result:
image

Desired result:
The output of both Total Number of Tray Seeds Planted and Average Seeds Planted per Hour should not be NaN (Not a number) but instead should be a proper number values.

Seeding Report: Inconsistent Date Order

Description

The seeding report is not ordered by the dates, but primarily by type of seeding and then by dates.

Directions to replicate the bug

  • Go to the FarmData2 website
  • Choose a tab BarnKit
  • Pick a sub-tab Seeding report
  • Choose a Start date 01/01/2019, and End date 12/31/2020
  • Scroll down until you find the place where date goes from year 2019 to 2020

image

Observed result

We can notice from the picture above that the date goes from 2020-07-10 to 2019-02-15.

Expected result

We expect the table to be sorted in order by date.

Seeding Report: NaN value on Tray Seeding Summary

Description:

In the Tray Seeding Summary table at the bottom of a Seeding Report, the "Total Number of Tray Seeds Planted" and "Average Seeds Planted per Hour" are reported as NaN(Not a Number) instead of proper values. The different behaviors seem to be dependent on the date range.

Steps to replicate:

  1. Log into FarmData2 with the correct user credentials.
  2. Click on the tab BarnKit and then click on Seeding Report.
  3. Set the Start and End date from 03/01/2019-06/01/2019 and proceed with clicking Generate Report.
  4. Scroll the page down to Tray Seeding Summary.

Observed Output:

image

Desired Output:

There should be proper values for the "Total Number of Tray Seeds Planted" and "Average Seeds Planted per Hour" instead of NaN.

Seeding report: Tray Seeding Summary Sorted date value

Description: the date column sorted the value incorrectly such that it can created confusion.
Recreate Bug:

  1. Visit BarnKit
  2. Enter date from 07/01/2019 to 07/15/2019

Screen Shot 2023-05-02 at 9 52 26 PM

observe output
Screen Shot 2023-05-02 at 9 53 32 PM

desired ouput: the column should be in the correct order by date.

Seeding Input: Duplicates appearing in Area Dropdown

The Area drop down in the Seeding Input form contains duplicates. The same list of areas appears to be being appended to the dropdown multiple times. Each Area should appear in this list only one time.

Steps to Reproduce

  1. Clear browsing data
  2. Visit Seeding Input form
  • Area's will be listed once.
  1. Visit a different tab (e.g. info)
  2. Area list will update with a second copy of all areas.
  3. Each visits to another tab and return to the Seeding Input form will add another copy of the areas to the drop down.

Based on the above behavior this appears to have something to do with the way the caching is done for areas. It should be compared to what is being done for the crops which are not exhibiting the same behavior.


Issue by braughtg
Tuesday Jun 07, 2022 at 13:06 GMT
Originally opened as DickinsonCollege#460

Seeding Report: Allowing Invalid Input that produces incorrect results

Description: The seeding report in Barnkit of FarmData2 produces incorrect results when invalid dates are entered for startDate and endDate, such as 02/31/yyyy - mm/dd/yyyy, 11/31/2021- mm/dd/yyyy (The characters in this two example can be represented by any month, date, or year). The invalid dates can only be entered by typing directly into the input box and cannot be achieved using the calendar function.

It seems like most of the errors occur because a nonexistent day in a month has been entered. Also, entering a day that has not happened yet will cause an error as well. When errors occur, the report that will be generated are all identical.

PS: The original farmdata1 might contain this issue as well. An invalid date such as February 31 can be used to search, but I cannot give a definite conclusion as I wasn't able to test further with the guest edition.

Directions to Reproduce:

  1. Open up the FarmData2 App and Log in
  2. Click on the BarnKit Tab
  3. Click on the Seeding Report Tab
  4. Enter the testing value in the start date and end date field
  5. Click on the generate report button

Expected result: Shown and described in the picture.
Error sample (expected result)

Actual result: Shown and described in the pictures.
Error sample 1
Error sample 2


Issue by WilliamC529
Friday Apr 29, 2022 at 16:45 GMT
Originally opened as DickinsonCollege#451

Seeding Input: restructure order of Inputs

The Data section should be broken up into two sections, with the date, crop, comments, and area in the first section. The second section should have everything else and be after the Tray/Direct Seeding section. The second section should be called something other than data.

reorderingDataInputs

To test this go to the Seedings Input subtab under FieldKit tab, which is on the home page.

The code can be found by going to farmdata2_modules/fd2_tabs/fd2_field_kit/seedingInput.html file.


Issue by IrisSC
Friday Jul 23, 2021 at 20:30 GMT
Originally opened as DickinsonCollege#273

Seeding Input: Allows invalid inputs

Description: When creating a new Seeding Input Log, it is possible to enter values that are invalid, such as negative numbers and decimal values that do not make sense in certain categories (e.g. Workers: 9.4).

Directions to Replicate the Bug

  1. Open the FarmData2 Application
  2. Click on the Seeding Input button in the FieldKit Tab
  3. Select any Date of Seeding, Crop, Area, and choose either Tray Seeding or Direct Seeding
  4. Enter invalid values, such as negative numbers or decimal values
  5. Click Submit

Expected Results: The application should not let the user submit these values and should give the user an error message that notifies them of the appropriate values that they should input.

Observed Results: The application allows the user to submit these invalid values and stores this Seeding Input Log with the rest of the data.
image


Issue by goldberl
Saturday Dec 11, 2021 at 21:42 GMT
Originally opened as DickinsonCollege#333

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.