-
Notifications
You must be signed in to change notification settings - Fork 5
Logging improvements #9
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
Merged
Merged
Changes from 1 commit
Commits
Show all changes
21 commits
Select commit
Hold shift + click to select a range
593acf4
deepstate_datatype_check rewritten
FabrizioSandri d42efaf
no need to use an else-if. Avoid to call deepstate_datatype_check twice
FabrizioSandri 9a44dfb
return the mismatched datatypes
FabrizioSandri 0b4d2d9
print the list of mismatched datatypes
FabrizioSandri ad4bf24
removed unused code
FabrizioSandri b012edb
no need to import RInside
FabrizioSandri f76a7e1
verbose parameter
FabrizioSandri df138c9
roxygen documentation update
FabrizioSandri 72f564b
documentation files
FabrizioSandri f516aa0
Setup CI checks for this branch
FabrizioSandri 1d7e9cc
list_testfiles brackets fix
FabrizioSandri 91da805
mismatched datatypes fix
FabrizioSandri 6b85147
workflow run on every branch
FabrizioSandri 1c33720
mismatched datatypes improvement
FabrizioSandri 8efdebc
rename deepstate_get_unsupported_datatypes
FabrizioSandri e8a1a60
deepstate_fun_create improvements - table
FabrizioSandri 22def71
data table update
FabrizioSandri aa8639d
verbose parameter fix
FabrizioSandri 7b4d7e9
code refactoring
FabrizioSandri 95c3d88
analyze binary parameters fix
FabrizioSandri cda836b
run CI only once fix
FabrizioSandri File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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.
this is the list of supported data types right? So rather than "mismatched" in the function name maybe "unsupported" would be more appropriate?
Also this list is redundant with the logic in https://github.com/FabrizioSandri/RcppDeepState/blob/master/R/fun_harness_create.R -- if you have time it would be good to reorganize that code so that a list or table is used to lookup what to do, rather than the current code which is rather difficult to understand (lots of if/else statements).
Uh oh!
There was an error while loading. Please reload this page.
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.
That's true, this list is redundant. I updated the
deepstate_fun_createfunction inside fun_harness_create.R and replaced the if else statements with a table containing information for the supported datatypes. In detail each column of this table corresponds to a supported datatype and provides some details on it. The first row of this table contains an alternative datatype to be used when saving the inputs(e.g., usingqs::c_qsave), whereas the second row correspond to the associated generation function that takes as input a range. When a datatype contains a value of NA in both rows, it means that is supported, utilizes itself when executingqs::c_qsaveand lacks a range function. In this way checking if a datatype is supported is really simple: just check if exists a column for the datatype in this table.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 think the function
deepstate_get_unsupported_datatypesmay now be removed.