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
During development of ADaM programs, when not all variables existing in the specs have been derived yet, it is so annoying that check_variables function fails with error and stops execution. Same for ongoing work. Someone adds a new variables to the specs and ADaM program no longer works. What's the point to fail with error just because there is one variable not derived? Shouldn't it be a warning?
Same for check_ct_data. We're far away from eSub and do not want to clean up our specs now by adding all CTs etc. We'll do it when ADaM is final. Until then we'd like to see a warning, not an error.
Our temporary solution is to add the following in .Rprofile:
During development of ADaM programs, when not all variables existing in the specs have been derived yet, it is so annoying that
check_variables
function fails with error and stops execution. Same for ongoing work. Someone adds a new variables to the specs and ADaM program no longer works. What's the point to fail with error just because there is one variable not derived? Shouldn't it be a warning?Same for
check_ct_data
. We're far away from eSub and do not want to clean up our specs now by adding all CTs etc. We'll do it when ADaM is final. Until then we'd like to see a warning, not an error.Our temporary solution is to add the following in
.Rprofile
:The text was updated successfully, but these errors were encountered: