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
@zuzulaz commented on the quality check protocol: "Maybe you deal with this already, but as I am not familiar in detail with the checks, I rather ask: is there any check to verify if both dates are from the same year – that there is not any error for example in the year of one of those dates? For example, it might happen that lay date is noted as 10-04-2018 and hatch date as 25-04-2019. This would mean that lay date is earlier – what would meet the assumption, however, there is an error in the hatch/lay year.
The same would apply for the B5 check.
More generally, is there any check to check for the coherence of dates (within the year/population)?"
I first thought of including this in the existing B4 and B5 checks, but now I consider creating a new check that compares the years of LayDate_observed, HatchDate_observed and FledgeDate_observed to BreedingSeason.
The text was updated successfully, but these errors were encountered:
@zuzulaz commented on the quality check protocol: "Maybe you deal with this already, but as I am not familiar in detail with the checks, I rather ask: is there any check to verify if both dates are from the same year – that there is not any error for example in the year of one of those dates? For example, it might happen that lay date is noted as 10-04-2018 and hatch date as 25-04-2019. This would mean that lay date is earlier – what would meet the assumption, however, there is an error in the hatch/lay year.
The same would apply for the B5 check.
More generally, is there any check to check for the coherence of dates (within the year/population)?"
I first thought of including this in the existing B4 and B5 checks, but now I consider creating a new check that compares the years of LayDate_observed, HatchDate_observed and FledgeDate_observed to BreedingSeason.
The text was updated successfully, but these errors were encountered: