This repository has been archived by the owner on Mar 18, 2024. It is now read-only.
Carbon flux: use latitude, longitude and day of year in predictions? #10
Comments
It's hard to see how the longitude will help anything, so I'd vote for not including it. |
In many places there are clear env gradients either in lat or lon. In
this specific case I am not sure if it would make a difference or if you
are working on a general tool.
…On Aug 16 2018 8:12 PM, James A. Bednar wrote:
It's hard to see how the longitude will help anything, so I'd vote
for not including it.
|
Right; over a relatively small region of the globe, lon would be a a perfectly reasonable feature to include. But for a global model, it just seems more confusing than helpful, likely to lead to overfitting and poor generalization, unless recoded as something like "distance from the nearest coastline" or something else more meaningful at a global scale. |
Agreed. Lon is more meaningful regionally (like the west coast of the
Americas, etc.). I was not sure if this was a specific case or if the
code was intended to expose/demonstrate API functionality. Sorry if I
threw up a red herring.
…On Aug 17 2018 7:14 AM, James A. Bednar wrote:
Right; over a relatively small region of the globe, lon would be a a
perfectly reasonable feature to include. But for a global model, it
just seems more confusing than helpful, likely to lead to overfitting
and poor generalization, unless recoded as something like "distance
from the nearest coastline" or something else more meaningful at a
global scale.
|
Any and all advice welcome!!! |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
I'd like a better explanation of the motivation, and some domain knowledge to know what variables to exclude.
The text was updated successfully, but these errors were encountered: