-
Notifications
You must be signed in to change notification settings - Fork 1
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
Download enhacements #166
Comments
@marieALaporte here you can attach the excel file |
🚫 This issues is not valid any more. Please check the next issue ⏭ #166 (comment)
We had a call with Brian and Medha this morning about the ''NumberofMeasurementperPlot''. In KDSmart, they add a # in the trait name to give the number of measurement per plot. I put an example in the attached file with 2 variables in yellow in the Trait List and in the Fieldbook tab. HEADER RULE IN FIELDBOOK:
|
METADATA
Residue management tab
Irrigation tab
Harvest tab
TraitList
|
|
|
|
|
|
Have different Ids, trait names and trait alias when a measurement is used for 2 crops in the same expriment. @celineaubert Thanks for reminding this issue. As we discussed in MPL, We are going to generate a random ID (for KDSMART) for all the traits in order to avoid duplications. |
Hi @omarbenites here is the last Header in fieldbook, in the Soil tab: Explanation for this choice from Brian It is better to use the "nPerSeason" to specify the "prefix" and the "nPerPlot" for the TraitInstance suffix. .---- nPerSeason () 2:PH <--- One click selects all the "children" ( ) 3:PH Each "nPerSeason" Trait collects its instances below it. Doing it the other way around the user would get: .--- this was where you had the "nPerPlot" ( ) 2:PH So to choose "nPerSeason==2" the user would have to expand each of the "nPerPlot" items and then choose the "__2" items individually. As you can image it gets even worse when you have nPerSeason==12 ! |
|
-Solved for the next update |
|
✅ fixed for the next update |
✅ @omarbenites In Intercropp, protocol info for the second crop is not exported in the Excel file. A: @celineaubert look that you should have not selected the check box to export the information |
Timing for Crop Measurement:
@omarbenites it is better to not have any prefilled value. |
Change the # for : ✅ Solved next update |
@omarbenites I have highlighted in yellow the tabs where the issues are. CRD_rice_issues in yellow.xlsx The issue for missing values in Traitlist for the measurement ''Plant density'' comes from AgroFIMS as it allows to select ''grain'' for ''Plant density''. However, in the Crop_measurement file in the Drive, '' Plant density'' is only for whole plant
|
✅ Fixed for the next update |
✅ Fixed for next update |
✅ Ready for the next update |
✅ fixed for the next update ✅ |
Please refer to the DataDictionnary when adding TraitLevel - TraitLevel for Phenology is Subplot Info in the DataDictionnary: Wrong info in Excel file exported from AgroFIMS ✅ |
|
@omarbenites
✅ |
current names --> Change to
|
✅ |
Management practices
✅ @celineaubert You mean in the |
@omarbenites |
✅ |
✅ |
|
[NOW FIXED! 👍 ]
Group
,Subgroup
, ...Label
Ex.
harvest_cm
12
The text was updated successfully, but these errors were encountered: