Age | Commit message (Collapse) | Author |
|
Issue:
https://github.com/genenetwork/gn-gemtext-threads/blob/main/topics/gn1-migration-to-gn2/partial-correlations.gmi
* Format the numbers for display, to reduce the number of columns
needed for display.
|
|
Issue:
https://github.com/genenetwork/gn-gemtext-threads/blob/main/topics/gn1-migration-to-gn2/partial-correlations.gmi
* Display the correlations results for "Publish" datasets.
|
|
Issue:
https://github.com/genenetwork/gn-gemtext-threads/blob/main/topics/gn1-migration-to-gn2/partial-correlations.gmi
* Add templates for the tables that will display the results.
|
|
Issue:
https://github.com/genenetwork/gn-gemtext-threads/blob/main/topics/gn1-migration-to-gn2/partial-correlations.gmi
* Add some html elements to be used to display the results of running
the partial correlations
* Provide some initial proof-of-concept javascript code to animate the
various elements and to use for displaying both successful and error
results.
|
|
Issue:
https://github.com/genenetwork/gn-gemtext-threads/blob/main/topics/gn1-migration-to-gn2/partial-correlations.gmi
* Using a tuple, rather than a list for the HTTP methods in the route
definition causes an error. This fixes that by using a list.
|
|
Issue:
https://github.com/genenetwork/gn-gemtext-threads/blob/main/topics/gn1-migration-to-gn2/partial-correlations.gmi
* Skip the target traits selection step, and only allow running the
partial correlations against one of the available databases.
|
|
Issue:
https://github.com/genenetwork/gn-gemtext-threads/blob/main/topics/gn1-migration-to-gn2/partial-correlations.gmi
* Separate the form elements that allow selection from the elements
that display previous selections.
This allows styling of the "active" area of the form in a different
way from the "display" area of the form, allowing the user to see
information on their previous choices, even while making further
selections for the partial correlations.
|
|
Issue:
https://github.com/genenetwork/gn-gemtext-threads/blob/main/topics/gn1-migration-to-gn2/partial-correlations.gmi
* Add UI elements to trigger the partial correlations feature
* Connect partial correlation view to the application
* Point to correct application element for gunicorn
|
|
This adds the "selected" class to rows selected by filterByIndex, which adds highlighting to them
I also made the variables in this part of the code camel cased
|
|
|
|
|
|
|
|
regex, for validating the Select Rows input
|
|
|
|
read and explicitly inverts start_index and end_index when the former is greater than the latter
|
|
change_buttons because it's referenced in many other files
|
|
|
|
|
|
hit Enter in the Select Rows text area
|
|
a little vertical space
|
|
text, in the hopes that this will show up normally for Rob
|
|
the user sorts)
|
|
By Index feature from the trait page; you can now use text indicating index ranges or specific indices, and the filter triggers on either hitting Enter or clicking outside of the text area
|
|
space
|
|
|
|
|
|
the Location text was being pushed to a second line (this was actually visible for me as well, not just Rob)
|
|
pushed onto a second line in some browsers (specifically Robs, but couldn't reproduce in mine, so I just changed it to something that should work for him)
|
|
superscript question mark, since the icon was appearing strangely in some browsers (namely Rob's) but in a while I couldn't reproducd
|
|
the Chr column (and the chr_num column isn't always populated for certain Genotype datasets)
|
|
scrolling
|
|
submitting search result traits to a collection; it previously just used JQuery and needed to be changed to use DataTables API to select from rows
|
|
Removed bonface's notebook until seaborn gets fixed.
|
|
* wqflask/wqflask/metadata_edits.py (update_phenotype): Filter out
values with |ε| < 0.001 when generating the diff file.
|
|
|
|
|
|
|
|
from being able to access all rows (which caused functions like Select All to only select the first 100-200 rows)
|
|
|
|
|
|
Prior to this, we only checked for the json files with contained the
modifications. However, in the case of double deletions, and double
inserts, the data would have been stored in the db anyway; which is a
false representation of changes.
|
|
Track any double-inserts or double-deletions
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|