-
Notifications
You must be signed in to change notification settings - Fork 2
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
Alternative risk-scaling functions #21
Comments
This is important since the linear scaling is very limited and very often totally inappropriate. However, I have some doubts about how to implement these alternatives. Particularly in the interface. The typical user of the interface already struggles with assimilating the linear scaling. How will they react towards a selection of sigmoidal, exponential, or step functions with two additional parameters One option would be to include the functionality in the package (for more advanced users), but not in the graphical interface (to keep things simple). Or we can include a hidden section in the interface labelled Advanced that can be expanded for setting these options. What do you think? |
during Annelise Tran's MCDA training, she does a strong focus on the
functions that link individual risk factors with the final risk.
the beginner is thus confronted to this major issue early in the process. I
am confident that the users will appreciate to be able to define it
themselves.
for the interface, I programmed during the Rshiny training session in
Reunion an option box (under the map with raw data) with radio buttons
(linear (as default), sigmoidal, exp or step), and additional input form to
enter x1 and/or x2 parameters (visible when step is activated). I added
also a check box to choose an inverse function or not. I try to send you a
screenshot example asap.
as a ccl, to include these functonnalities in the R code is a priority.
the "for advanced users" options in the interface could be an elegant
solution in a second step
v
Le mer. 10 avr. 2019 à 16:14, Facundo Muñoz <[email protected]> a
écrit :
… This is important since the linear scaling is very limited and very often
totally inappropriate.
However, I have some doubts about how to implement these alternatives.
Particularly in the interface.
The typical user of the interface already struggles with assimilating the
linear scaling. How will they react towards a selection of sigmoidal,
exponential, or step functions with two additional parameters x1 and x2
to deal with?
One option would be to include the functionality in the package (for more
advanced users), but not in the graphical interface (to keep things
simple). Or we can include a hidden section in the interface labelled
*Advanced* that can be expanded for setting these options.
What do you think?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#21 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/Au3qerGTMktRldZWzyzoZ2cQ_LxOS6Mhks5vfdW5gaJpZM4cmtMl>
.
--
*Vincent PORPHYRE*
CIRAD
Coordinateur du réseau QualiREG en Océan Indien
http://www.qualireg.org
------------------------------------------------------------------------
CIRAD - UMR 112 Systèmes d'élevage en milieux méditerranéens et tropicaux
Tel. +262.2.62.49.92.55 (office)
Fax. +262.2.62.49.92.95
Secr. +262.2.62.49.92.02
Mail. [email protected]
Website. http://pigtrop.cirad.fr
CIRAD - Station Ligne-Paradis
7 chemin de l'IRAT, F-97410 Saint Pierre
Réunion - FRANCE (DOM)
Website UPR. http://www.cirad.fr/ur/systemes_elevage
Perso page. http://agents.cirad.fr/index.php/Vincent+PORPHYRE
Trouver un projet ou un futur partenaire scientifique
en Océan Indien sur www.agro-oi.org
------------------------------------------------------------------------
Pensez à l'environnement : n'imprimez pas ce courriel !
Adopt the eco-attitude, Think Environment before printing
<http://www.qualireg.org>
|
Noted. Thanks. |
Currently, the only scaling functions are linear, with the option to be reversed.
Please add radio buttons to choose various links for standardization (see code at the end of this post, as a suggestion only)
Feature requested by @vporphyre in #19
The text was updated successfully, but these errors were encountered: