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

Fix v1.1.0 #117

Merged
merged 90 commits into from
Nov 12, 2024
Merged

Fix v1.1.0 #117

merged 90 commits into from
Nov 12, 2024

Conversation

mvarewyck
Copy link
Collaborator

No description provided.

@mvarewyck mvarewyck marked this pull request as ready for review September 27, 2024 15:30
@SanderDevisscher
Copy link
Collaborator

Copy link
Collaborator

@SanderDevisscher SanderDevisscher left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@mvarewyck when testing the bins for the invasion history I found some weird behaviour:

I'm testing with Lithobates catesbeianus

What happens:

  1. When I select "quantiles" BinType with the default nBins (=5) I get the following error:
    'breaks' are not unique
  2. I thus reduce the nBins to 4 which results in 4 bins see below:
    image
    but upon clicking binConfirm the binType switches to "user defined" and the last bin expands to [lower limit - max value] see below:
    image
    The issue does only occur the first time you click binConfirm. Changing the region seems to reset the issue.
  3. Typing custom bin breaks seems not to work fluently the textbox seems to unselect everytime I type a digit
  4. User defined bins are not reflected in bin graph, see below:
    image
  5. Last bin starts empty when binType = "user defined" falsely stating there is no data
  6. Last binSize readablility is poor
  7. Legend & bins do not match, see below:
    image
    image

What should happen:

  • 1. Quantiles implies 4 bins so nBins slide should be disabled for quantiles and it should be fixed to 4
  • 2. The bin sizes should remain fixed once binConfirm is clicked
  • 3. Typing in bin breaks should go without a hitch
  • 4. user defined bins should be reflected in graph
  • 5. last bin should start with max value
  • 6. if possible change last binSize text color to white ?
  • 7. Bins should be included into the legend even if they are empty

Copy link
Collaborator

@SanderDevisscher SanderDevisscher left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

  • The Harmonia+ link should be placed under risk assessment
  • The Harmonia+ link should get "Harmonia+ Risk Assessment" as link text

@mvarewyck
Copy link
Collaborator Author

  1. Quantiles implies 4 bins so nBins slide should be disabled for quantiles and it should be fixed to 4

Quantiles can be any number of groups. Quartiles are fixed to 4. So, unless you still want to change, for now I still allowed values different from 4.

  1. last bin should start with max value

When choosing user-defined, we currently take hard-coded break values as defined in the past for the groups, depending on the chosen unit for outcome. If needed, we can change this to depend on the data, e.g. taking quantiles as first suggestion for the breaks which can be further modified by the user. Also, for user-defined both the labels and values can be changed by the user, so 'name' and 'break' will not necessarily match (freedom to the user).

Copy link
Collaborator

@SanderDevisscher SanderDevisscher left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@mvarewyck in the latest version it looks like you moved the whole links page to the risk assessment page. it should be displayed only on the links page.

@SanderDevisscher
Copy link
Collaborator

  1. Quantiles implies 4 bins so nBins slide should be disabled for quantiles and it should be fixed to 4

Quantiles can be any number of groups. Quartiles are fixed to 4. So, unless you still want to change, for now I still allowed values different from 4.

My bad 😅 ok like it is now!

  1. last bin should start with max value

When choosing user-defined, we currently take hard-coded break values as defined in the past for the groups, depending on the chosen unit for outcome. If needed, we can change this to depend on the data, e.g. taking quantiles as first suggestion for the breaks which can be further modified by the user. Also, for user-defined both the labels and values can be changed by the user, so 'name' and 'break' will not necessarily match (freedom to the user).

After meeting with @soriadelva we think using "uniform" with 4 bins as first suggestion is the best starting situation.

Additionally there are some other remaining issues, namely

  • typing a name has the same issues with usability like breaks (which is fixed now).
  • since names & breaks are unrelated I would suggest displaying both in graph if they are not equal (bvb lage aanwezigheid (0-44))

Copy link
Collaborator

@SanderDevisscher SanderDevisscher left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

"Aantal nieuw geïntroduceerde soorten per jaar" throws an error stating non-numeric argument to binary operator

@SanderDevisscher
Copy link
Collaborator

"Aantal nieuw geïntroduceerde soorten per jaar" throws an error stating non-numeric argument to binary operator

same with Cumulatief aantal geïntroduceerde soorten

Copy link
Collaborator

@SanderDevisscher SanderDevisscher left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Bij "Geïntroduceerde soorten per introductieroute (CBD, niveau 1) - trends" I get the following message and no graph:
In argument: bins_first_observed = floor((.data$first_observed - from)/bin) * bin + from.

@mvarewyck
Copy link
Collaborator Author

"Aantal nieuw geïntroduceerde soorten per jaar" throws an error stating non-numeric argument to binary operator

It's due to new "data_input_checklist_indicators.tsv" data which was not created with the latest createTabularData() function yet. I've updated by hand once.
https://github.com/inbo/alien-species-portal/blob/fix_v1.1.0/alienSpecies/R/data_create.R#L472-L473

@mvarewyck
Copy link
Collaborator Author

Bij "Geïntroduceerde soorten per introductieroute (CBD, niveau 1) - trends" I get the following message and no graph: In argument: bins_first_observed = floor((.data$first_observed - from)/bin) * bin + from.

It was due to the same data issue: first_observed was no longer numeric - fixed now

@SanderDevisscher
Copy link
Collaborator

SanderDevisscher commented Oct 23, 2024

Both issues with data types seem fixed. I'm testing if the files get overwritten by the github actions if they are run with the alienspecies version from this branch.

upload_files_processing
upload_files_direct

These issue still remain though:

  • typing a name has the same issues with usability like breaks (which is fixed now).
  • since names & breaks are unrelated I would suggest displaying both in graph if they are not equal (bvb lage aanwezigheid (0-44))

@mvarewyck
Copy link
Collaborator Author

  • typing a name has the same issues with usability like breaks (which is fixed now).
  • since names & breaks are unrelated I would suggest displaying both in graph if they are not equal (bvb lage aanwezigheid (0-44))

That's correct, I'm still improving the bins selection

@SanderDevisscher
Copy link
Collaborator

The data seems to not be overwritten by the aspbo github actions 🥳

@mvarewyck
Copy link
Collaborator Author

@SanderDevisscher I've implemented all changes.

@SanderDevisscher
Copy link
Collaborator

Deploying to uat .github/workflows/deployment_uat.yml

@SanderDevisscher SanderDevisscher merged commit ace30bc into uat Nov 12, 2024
1 check passed
@SanderDevisscher SanderDevisscher deleted the fix_v1.1.0 branch November 12, 2024 14:33
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

Successfully merging this pull request may close these issues.

2 participants