-
-
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
update egt05 #535
update egt05 #535
Conversation
🧪 Code Coverage Summary
Diff against main
Results for commit: 18e64a932a384a95c9da4b3a50d97d7d39fe3368 Minimum allowed coverage is ♻️ This comment has been updated with latest results |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'm getting the below immediate error,
Error:
! adam_db$adeg$AVALCAT1
is not of type factor
this means that AVALCAT1 has to be of type factor, so after converting it to factor it will work. The reason to only allow factor is that the order is very important and we can't specify order for each parameter (if there is split_rows_by(PARAMCD)). we must make sure the order is correct (at least within each subgroup of data) and prune the 0 rows) |
Thanks @clarkliming , yes I understand this, but this should be within egt05_pre shouldn't it? Otherwise this will fail everytime for every user unless they update their data? |
this is really study specific: if we convert it to factor in pre, it is likely that the order is totally wrong. In my design, users should create script for this |
Hi @clarkliming - this is the only template I've seen where we expect it to fail every time until the user does a step that is not automatic/instructed. Is this correct? Can we not set to a factor so the template runs, and then the user can determine the order after review? Of apply the order based on what we know already in standards (ie. '<=450 msec', '>450<=480 msec', '>480<=500 msec', '>500 msec') |
retriction has been loosen so it should work by default |
Thanks @clarkliming , I now get the below error which is due to CHGCAT1 not present for BASELINE
|
oh this reminds me why I add this restriction. AVALCAT1 and CHGCAT1 are needed to be valid values but rtables is not taking "" as valid values, and in SAS data it has to be "". We need to add a step of converting "" to NA in pre functions |
please note that there are still issues in rtables so the page_by is not correct right now |
Thanks @clarkliming . A couple of observations,
|
it should return all levels; could you please provide your example and expected output?
will be fixed |
Example using prune_0, I was thinking all levels for AVALCAT1 and CHGCAT1 would appear for every visit?
|
hi @barnett11 this is what I get could you please reinstall latest and restart session and try again? (and I think this table with prune_0=F is not correct, it may display other categories that is not for the parameter) |
Indeed @clarkliming , it doesn't work very well for what the user may intend. I still cannot get every category displaying, the below is what I get currently,
and then with applying factor myself it works better,
|
@barnett11 I get your point. Actually, I did not convert anything to factor. characters are allowed here. I totally understand your concern that the rows are not printed( and if you may run into issues if a level is only owned by a arm, which I think is not so good). I wonder, shall we provide some documentation to say that, please use 'factors' if custom sorting is needed? and we still allow the variables to be in character? |
Yes, as long as the user knows how to achieve this then that's fine, documentation would suffice |
@barnett11 documentation added; and let's don't wait for tern's bug (anyway we can, by default don't use page by) |
🧪 Code Coverage Summary
Diff against main
Results for commit: b85463c627d3140d308312a9d3b90431cc956fd6 Minimum allowed coverage is ♻️ This comment has been updated with latest results |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Please see related PR: insightsengineering/dunlin#106
Nice to see this template being finalized
Co-authored-by: b_falquet <64274616+BFalquet@users.noreply.github.com> Signed-off-by: Liming <36079400+clarkliming@users.noreply.github.com>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Lovely, that's looking really good now thanks
close #413
in preprocessing, remove filter of PARAMCD == "QT" (users could use filters or in pre function to modify it)
also split parameter by page
found bug and raised at
insightsengineering/rtables#653
also blocked by
insightsengineering/rtables#651