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

variable requirements: experimentId #395

Open
anxcon opened this issue Oct 2, 2015 · 6 comments
Open

variable requirements: experimentId #395

anxcon opened this issue Oct 2, 2015 · 6 comments

Comments

@anxcon
Copy link

anxcon commented Oct 2, 2015

variables for things like atmo pressure, ambient temp, gravity, etc
something in RPM cfg to put experimentId, when no gadget onboard and if experiment not filled for that altitude (and biome if applicable) then say N/A or such, if experiment filled or have gadget then show value

can go further and look at % of experiment filled, and add an error rate to the value

for cfg, thinking just something basic
variablename = experimentId
that way it can be expanded for other experiments people might come up with
such as fuel science mod testing fuels, could effect a variable used in dv formula

@MOARdV
Copy link
Collaborator

MOARdV commented Oct 2, 2015

I don't quite understand what the feature you are asking is. Is it a variable? More than one variable? Something other than a variable?

@anxcon
Copy link
Author

anxcon commented Oct 2, 2015

RPM variables for making the displays, just give the values, such as ATMPRESSURE gives atmo pressure, whether or not any related tools are onboard (such as the stock sciencey toy for measuring pressure)

i'm basicly asking for optional pre req to be added, to allow it to display, in this case it would be a part with ModuleEnviroSensor turned on, or if a previous measurement was taken (checking experimentId barometerScan for progress for current biome/situation)

if we can link the variable to experimentId ourselves when making the displays, then anyone could expand it with all the sciencey toys that exist :)

@MOARdV
Copy link
Collaborator

MOARdV commented Oct 2, 2015

Okay, I understand now. That could be very difficult to do, since there are hundreds of variables in RPM. It would be easier to use the new SELECT_ variables to customize results, although that will still require a way to know if a particular experiment is available. I will need to think about how I would do this.

@anxcon
Copy link
Author

anxcon commented Oct 3, 2015

read through wiki again and couldn't find info on SELECT_ variables?

but that combined with a variable to see current/max/0-1 progress of an experimentId in the current biome/situ sounds like itll work :)

but then this should probably be split into 2 issues?

  1. variable to see experimentId progress
  2. variable for true/false to see if ModuleEnviroSensor(of type) is on vessel and active

@MOARdV
Copy link
Collaborator

MOARdV commented Oct 4, 2015

Select variable is here: https://github.com/Mihara/RasterPropMonitor/wiki/Custom-Variables#creating-a-select-variable

Not clearly documented - that's one of my upcoming tasks, to make it easier to find things since this mod has grown so much.

As for the experiment progress and sensor type info, that should be fairly easy to add. That's been one of the things I've been meaning to add for a long time, but I do not spend much time playing career, so I never knew what needs to be added for science.

@anxcon
Copy link
Author

anxcon commented Oct 5, 2015

for science variables
current progress value (i would say in current biome/situ)
max value obtainable (again for current biome/situ)
could have a transmit value
"can perform here" (for current biome/situ)

but the way custom variables work, makes me think that style works better than single variables per field

RPM_EXPERIMENT_VARIABLE
{
name = SCIENCE_VALUE
experimentId = GooExperiment
biomeId = BIOMEID (if you want it to current variable to fetch data based on current biome, or have some other variable used say custom one that translates long+lat into biome)
situation = SITUATION (same reasons)
type = CURRENT (current, max, transmit multiplier, etc)
}

just what i thought of after a day, i dunno

@MOARdV MOARdV removed their assignment Mar 28, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants