I do this kind of thing under control of make. If you organize the
individual pieces as separate targets then make -k will keep going and
make -j can be used to run things in parallel. R can be made to throw
an error with something like this:
egTarget:
@$(MKDIR) $(FLAGS)
It is probably not too difficult to do. You put the code that might
fail inside a "try({...})" and then test for failure. If it fails,
you can send an email and then continue to the next file. The actual
code would be dependent on where the error(s) might be occurring and
what you want to do on
Dear useRs:
Please provide me with your thoughts on an issue related to the design of a
production level system. For example, letÂ’s suppose that I need to run the
same R script for a finite sequence of items (e.g., in the energy industry, I
may need to asses the profitability of all gas stations
3 matches
Mail list logo
