alteryx / alteryx/AlteryxPrescriptive

Integer types not being handled on the R side

Aperta
#27 1 commento 0 reazioni 1 assegnatario Rivendicata da @ramnathv Vedi su GitHub
bug
Lingua principale
R
Stelle
3
Fork
5
Metriche di merge delle PR
Nessuna PR unita negli ultimi 30g

Descrizione

In the CPLEX spec, an Integer type field is technically categorized as "General", but on the UI side we call it "Integer" so that things are clearer. However, the R code is not currently looking for anything called "Integer", and so that type is not being processed correctly.

For example, the UI provides an array of field item objects, like so:

``` JSON
[
{
"fieldName": "x1",
"type": "Continuous",
"lowerBound": 0,
"upperBound": "+inf"
}, {
"fieldName": "x2",
"type": "Integer",
"lowerBound": 0,
"upperBound": "+inf"
}, {
"fieldName": "x3",
"type": "Binary",
"lowerBound": 0,
"upperBound": 1
}
]
```

The R code, found [here](https://github.com/alteryx/AlteryxPrescriptive/blob/28f4568ad2ba7c2d3f91efc90a9ed62ae5c0b962/R/manualInputs.R#L17-L26), is attempting to match on different field types, but is not looking for "Integer", and so everything falls through to the default case and is treated as continuous.

Guida per i contributori

Nessuna guida per i contributori indicizzata per questo repository

Valutazione

Questa issue non è ancora stata valutata.

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.