You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Not a real issue (the issue was in fact in my own script), but maybe a source of confusion.
All crop and livestock have income converted in lcu per year and stored in a variable ending by ‘income_per_year’, apart of : livestock_sale_income, meat_sold_income, bees_honey_sold_income.
It might be worth repeating the information (create a new column) or rename the column to add the suffix ‘_per_year’. This would avoid confusion and simplify the calculation of total income per year.
The text was updated successfully, but these errors were encountered:
So for the dataset that you have, there should also be extra data sets (e.g. stored in a folder called crop data) where all of these variables have been put into a simple table (e.g. a table of crop yield for individual crops, a table for crop income for individual crops). Our hope was that people would use these to get the key information they needed. We can talk more about this in today's coworking session if you are around?
Not a real issue (the issue was in fact in my own script), but maybe a source of confusion.
All crop and livestock have income converted in lcu per year and stored in a variable ending by ‘income_per_year’, apart of : livestock_sale_income, meat_sold_income, bees_honey_sold_income.
It might be worth repeating the information (create a new column) or rename the column to add the suffix ‘_per_year’. This would avoid confusion and simplify the calculation of total income per year.
The text was updated successfully, but these errors were encountered: