Comments (6)
Interesting, I feel like they have basically the same connotation to me (a prediction feels just as likely in my head to be some qualitative statement).
I just looked into this a bit more; at very least, wikipedia kind of disagrees with me. But wikipedia also seems kind of confused.
https://en.wikipedia.org/wiki/Forecasting
Forecasting is the process of making predictions based on past and present data.... Prediction is a similar, but more general term... for example, in hydrology the terms "forecast" and "forecasting" are sometimes reserved for estimates of values at certain specific future times, while the term "prediction" is used for more general estimates, such as the number of times floods will occur over a long period.
But on the prediction page:
https://en.wikipedia.org/wiki/Prediction
A prediction (Latin præ-, "before," and dicere, "to say"), or forecast, is a statement about a future event or data.
I think there's generally not much consensus on this.
from metaforecast.
How about "Question", "outcomes" and "estimate" as more specific versions of "Forecast", "options", "individual forecast"? Not sure how stable these would be, though.
Tagging @OAGr in case he has better options
from metaforecast.
I'm also curious what @uvafan thinks here.
from metaforecast.
I'd go with with "Question", "outcomes", "forecast". Btw, I think num forecasters is likely a better proxy for quality and more easily understood than num forecasts, when available.
from metaforecast.
"Question" / "Outcome" / "Estimate" seem good to me. "Forecast" instead of "estimate" is also okay.
I think I prefer "prediction" more than "forecast", because "forecast" is often used more more broad ways. (Like, you could have a "forecast" that's just a paragraph of text explaining how you think the world will be.)
In the case of Metaforecast, we're really handling "estimates" instead of just forecasts, so having a more generic term could be good.
Another thing we could do, in the backend at least, is to have more specific terms, like, "Estimand" or "Estimatable" (Or, "Forecastable". My guess is that this isn't needed at this point.
from metaforecast.
Oh yeah I agree with "Estimate" if some of the stuff in Metaforecast isn't forecasts about the future.
I think I prefer "prediction" more than "forecast", because "forecast" is often used more more broad ways. (Like, you could have a "forecast" that's just a paragraph of text explaining how you think the world will be.)
Interesting, I feel like they have basically the same connotation to me (a prediction feels just as likely in my head to be some qualitative statement).
from metaforecast.
Related Issues (20)
- Estimated timeline until graphql API? HOT 1
- Dashboard ids hashing leads to unexpected UX HOT 1
- Heroku not automatically building from Github HOT 2
- Add history to the graphql API HOT 2
- Documentation for grapqhl usage HOT 5
- Thoughts on next steps? HOT 4
- Fetchers status page
- fix platform fetching errors HOT 2
- Metaculus community forecasts are flipped HOT 1
- Create an embeddable chart page
- Make question page a bit nicer. HOT 4
- Smarkets: missing contracts HOT 9
- Add new questions page to API HOT 6
- "GraphQL query for this page" button
- Capture question chart instead of question card HOT 2
- Feature requests: display closed/resolved forecasts + filter forecasts by date opened
- Insight prediction API produces an error when ordering markets by is_resolved HOT 1
- GraphQL error: "Cannot use 'in' operator to search for 'hasNext' in undefined"
- Link in about section goes to localhost HOT 1
- Star rating filter not working as expected HOT 1
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
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.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from metaforecast.