
The build above represents my first thoughts on the macrophage in the context of TB. At one level the story here is quite simple.
Mycobacterium tuberculosis avoids destruction by blocking fusion of the phagosome with the lysosome wherein are located killing mechanisms for bacteria. The host raises its game by activating the macrophages but in some cases a proportion at least of the bacteria survive and the host walls them off in granulomas. So long as host immunity remains strong, the containment continues though there is always the possibility that reactivation may occur. With HIV infection, that probability is a high as 10%
annually.
What isn't fully understood is the detailed mechanism of the fusion block and the range of survival strategies used by the bacterium to persist in the macrophage. Accordingly, I decided to make the build more conceptual than representational and put it in the data-oriented Bioscape rather than Cellscape (though I need something there too).
I've opted initially for a more immersive style, if only to add variety. The image shows, for example, multiple entry pathways into the macrophage depending on the surface receptor used. The pathway used is not without consequence in terms of triggering defence mechanisms. The eventual build is likely to be much larger and visitors should note that it will probably be a while before anything worth exploring is available.
While moving into the build is intended to reflect the spatio-temporal progression of the bacterium within the macrophage, I'm undecided as to how to use the vertical walls. Those blocking the avatar path might represent compartments and/or macrophage defence mechanisms that the pathogen must subvert while the lateral ones could either be more informational and/or represent other contextual features beyond the macrophage such as T-cells. Either way, the walls are likely to be dynamic.
At present there are two levels. I'm wondering whether I should use this to reflect the state of the host and pathogen or different states of the macrophage, e.g. post-activation. I can't rule out using the z-axis to represent alternatives later in the build so I am presently a little ambivalent on this.
The avatar rides a two-seater hover platform (the "HoverBug") modified from the examples accompanying Jeff Heaton's book and available inworld from Encogia (
slurl). The particle jets were generated using Jopsy Pendragon's rather splendid
Porgan 1800. I am rubbish at particles and the Porgan, while not cheap in SL terms and with some limitations, makes their production significantly faster.
At present the bug's inventory can be loaded via avatar inventory with prims rezzed from the giant genome and elsewhere. The idea is that these represent virulence factors (VFs) that interact in some fashion with the build. VFs are selected using a dialog with the one currently chosen shown as temporary hovertext on the bug. Eventually I'd like the bug to reflect its current state and host interactions in a little more detail but this will have to do for starters.
How might this be used with students? Well, they could use the build as a maze, deploying VFs to negotiate the vertical walls. I wonder if this approach will be too 'clunky'/boring? Adding a game element (a health status for the bug maybe) might be worth considering. The VFs are, I guess, the equivalent of weapons though my gaming expertise is very limited and dated.
An alternative might be to leave the platform/bug in a particular state/location and ask students for their interpretation of events past and present; a distant analogy here is to the impressive Kristallnacht build (
slurl).
Bugs could also be preloaded and/or carry the products of
mutated genes. The macrophage might likewise be customised or augmented. Given the capacity for personalization, there would be merit in bringing the students together for debriefing.
I think it worth persevering with this a little as the movement of pathogens within cells, be they bacteria or viruses, is a significant topic. Having said that, hitting the right balance between complexity and intelligibility without overinterpreting current knowledge is a major challenge.
Ultimately it would be good to see student-generated builds of this type. I've just registered for a trial hosted
PIVOTE account with Daden and it may well be that this will play a significant (*cough* pivotal?) role in future developments. We shall see...