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

Input and output data need text descriptions #214

Closed
eliotmcintire opened this Issue Aug 10, 2015 · 3 comments

Comments

Projects
None yet
2 participants
@eliotmcintire
Contributor

eliotmcintire commented Aug 10, 2015

This is necessary to build a modular SpaDES ecosystem so that other people's modules inputs and outputs can be used as goals for inputs and outputs of new modules.

@achubaty

This comment has been minimized.

Contributor

achubaty commented Aug 10, 2015

this should all be part of the .Rmd file accompanying the module

@eliotmcintire

This comment has been minimized.

Contributor

eliotmcintire commented Aug 11, 2015

I think that is not enough... why not mirror the defineParameter(...
desc="")? Because the rmd manual doesn't have to exist or be written.

I believe that eventually, we will do more automation of the input and
output objects, so it is more than just name and class. This is not a high
priority, but it will be a major component of really extending the
integration of different modules from different users. We have discussed
this and we converged on the current situation, where we let the module
internally to do object checking. But that may not be the best way. We
shall see.

On Mon, Aug 10, 2015 at 7:54 PM, Alex Chubaty notifications@github.com
wrote:

this should all be part of the .Rmd file accompanying the module


Reply to this email directly or view it on GitHub
#214 (comment)
.

@achubaty

This comment has been minimized.

Contributor

achubaty commented Oct 29, 2015

merged into #189. closing.

@achubaty achubaty closed this Oct 29, 2015

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment