-
Notifications
You must be signed in to change notification settings - Fork 24
Added support for mvscmd #66
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
base: main
Are you sure you want to change the base?
Conversation
1441d17 to
1c9fb74
Compare
Create something that hides some of the complexity associated with creating ddd. Signed-off-by: Frank De Gilio <[email protected]>
Removed extra print statement Signed-off-by: Frank De Gilio <[email protected]>
08fbeb1 to
2aa7283
Compare
|
Hey - @AnthonyGiorgio can you review this and let me know? |
| dd_list.append(DDStatement("SMPLOGA","DUMMY")) | ||
|
|
||
| # Define the Global CSI | ||
| dd_list.append(DDStatement("SMPCSI",DatasetDefinition("AT4SMP.GLOBAL.CSI"))) |
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 dataset name looks rather specific. Is there a better way than hardcoding it?
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.
We should discuss this. I used what is in the main for my testing. The dataset name is not the only thing that is hard coded. Does it make sense to build a more complex main that takes parameters for all of the hard coded items - Or is it smarter to build a comment section that describes it better. The idea is to get people to use each of the functions rather than use them as part of the main.
Signed-off-by: Frank De Gilio <[email protected]>
Create something that hides some of the complexity associated with creating dds.