Giter Site home page Giter Site logo

researchmap's People

Contributors

arashsoft avatar armandidandeh avatar j0h4x0r avatar kb19 avatar pparsons avatar

Watchers

 avatar  avatar  avatar

researchmap's Issues

Non-analyzable awards

The issue wit non-analyzable awards still remains.
As far as I can remember, the dbclick action was supposed to be deactivated for these awards.
However, as you can see in the screenshot below, it is still active.

screenshot from 2014-12-31 14 09 43

error after deselecting co-authors

double click on a grant. then deselect some co-authors and click submit. then we have only a blank screen. Arash says no data is being returned.

Award related information box

Please do not read for the keyword from couchdb.
Instead, use analyzed_award._keyword.

Also, in case you feel it won't take too much space, you could also use analyzed_award._ldaResult for showing extracted topics from the award.
In this case, and for now, only show the first topic, i.e. analyzed_award._ldaResult[0]. This object of the array has tuples in the form of <term,probability>.

It is up to you to decide if we want to show this, and if yes, whether term only, or both.

BTW, for each publication, we can have the same; just in case!

grant circle size and amount

Can we do something about the grant-amount text coming out of the circle? Maybe make the text smaller or make the circle bigger? Just something to make it look better.

screen shot 2015-01-01 at 11 36 52 am

investigator-author mismatch

In the grant-pub analysis view, there seems to be a bug in returning the publications. For some reason the matching of names is off.

Investigator is Grbic, but all publications are from Goodale:

screen shot 2015-01-01 at 11 31 58 pm

Same with another grant from same PI:
screen shot 2015-01-01 at 11 33 34 pm

With this one the PI is Huner but author is Huang:
screen shot 2015-01-01 at 11 36 46 pm

Also look at this one. It is from Mike Bauer, but all pubs look like they have to do with chemistry:
screen shot 2015-01-01 at 11 39 22 pm

fix publication circle size

The size of the circles (publications) in the analytics area should be fixed. Currently, the size is set according to the number of publications returned. This makes sense if we want to avoid clutter when many publications are returned (by making the circles smaller). However, the changing size may confuse the user. Additionally, when a small number of publications are returned, the circles are too big and cover the grant circle (see image below). Do you think we should make them a constant size?

screen shot 2014-12-30 at 1 21 30 pm

Wrong parameters on function calls

When you deactivate some author/keyword for an award, if you select a new award, those inactives should not be passed to the function, should they?!

Consistency problem with the list of co-authors

I will work on the issue regarding the long list of co-authors this afternoon and evening.

In the meantime, if Arash has anything to change, or if Paul wants to test and find some bugs, let me know here.

Parameters not showing change in results

Due to what @pparsons and I discussed a while ago, I am attaching some screen shots after applying some changes.
The first 2 are using linear:

screenshot from 2015-01-02 15 33 07

screenshot from 2015-01-02 15 33 12

And these 3 are using sigmoid:

screenshot from 2015-01-02 15 33 18

screenshot from 2015-01-02 15 33 22

screenshot from 2015-01-02 15 33 28

However, there is a bug from the db, which when fixed, will show more of this effect.

If @pparsons is in a hurry, I suggest showcasing this functionality using this specific example as it is only returning one publication, and hence, following the changes much easier.

If not, then I am on it after having a late lunch right now/

Broken view after latest commits on December 31 at around 19:55

screenshot from 2014-12-31 20 23 32

It is possibly related to these three commits:

Stop double-click for Non-analyzable awards #7
Read award keywords from arman result instead of couchdb #5
Smaller radious for circles and minimum stoke for lines

As you can see on the terminal on the right hand side, the results is returned, so the analysis.js script is functional.
You can see that even the award information box is not showing any data, which means the UI is the source of issue.

Commit: Increase the gap between grant and publications to fix overlap #1

I am using this updated code, but looks like these gaps are not enough. See attached:

screenshot from 2014-12-31 15 00 32
screenshot from 2014-12-31 15 00 47
screenshot from 2014-12-31 15 00 51
screenshot from 2014-12-31 15 01 07
screenshot from 2014-12-31 15 01 11
screenshot from 2014-12-31 15 01 20
screenshot from 2014-12-31 15 01 32
screenshot from 2014-12-31 15 01 37

Also, again for the last screenshot, I see no links for most of the publications. Since this is only happening for topic modelling, does it mean that topic modelling is returning a very small radius value? I am not sure if you are putting these values into a scale before assigning them to the like stroke.

Changes to the Analytics control box

I am changing the confidence levels a bit, and hence we might need a modified version of the control box.

What I have in mind is like this:

Assuming we have 3 algorithms to choose, the first look will only show the publication years slidebar on top and then the algorithm selections and nothing more (no aggregation of confidence).
The once the user chooses one of the algorithms, the parameters that are related to that algorithm will show in a dropdown manner. This helps make sure that for the coming algorithm(s), the parameters will not have conflicts, and then we need not deactivate some parameters for those algorithms that do not use those parameters.

So it will be like this:


Analytics

 Publications (the slider bar)
 Algorithms (Exploration, Keyword Matching, Topic Modelling, etc. each as a radio button)

Then once one selects a radio button, the parameters for that algorithm will show up.

password is too easy to hack

This is a very minor issue but I think since we are open to the web now the password should be changed. Currently it's very easy to do a brute force dictionary hack.

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.