Hi @mmollina
Since I prefer to organise complex workflows like mapping in targets pipelines, I am interested to discuss what would be the best ways to work with mappoly2 objects and workflows.
It was very difficult to do this in mappoly due to references to external objects.
Are all the mappoly2 objects self-contained, and thus suitable for being persisted as targets objects?
What should we consider in terms of the functional style of mappoly2? More specifically Im trying to understand the idiom that you use use of sequential updates to an object as below. Im assuming that each of these calls is updating a specific slot, and that we want to avoid copying a large object?
#> Multi-locus map estimation
s <- mapping(s, type = "mds", parent = "p1", ncpus = ncores)
s <- mapping(s, type = "genome", parent = "p1", ncpus = ncores)
s <- mapping(s, type = "mds", parent = "p2", ncpus = ncores)
s <- mapping(s, type = "genome", parent = "p2", ncpus = ncores)
Hi @mmollina Since I prefer to organise complex workflows like mapping in targets pipelines, I am interested to discuss what would be the best ways to work with mappoly2 objects and workflows. It was very difficult to do this in mappoly due to references to external objects.