next up previous 264
Next: Managing Transformation Routines in Libraries
Up: Creating Your Own Private Mappings (IntraMaps)
Previous: Simplifying IntraMaps


Writing and Reading IntraMaps

It is most important to realise that when you write an IntraMap to a Channel ([*]), the transformation routine which it uses is not stored with it. To do so is impossible, because the routine has been compiled and loaded into memory ready for execution before AST gets to see it. However, AST does store the name associated with the transformation routine and various details about the IntraMap itself.

This means that any program attempting to read the IntraMap ([*]) cannot make use of it unless it also has independent access to the original transformation routine. If it does not have access to this routine, an error will occur at the point where the IntraMap is read and the associated error message will direct the user to the author of the transformation routine for more information.

However, if the necessary transformation routine is available, and has been registered before the read operation takes place, then AST is able to re-create the original IntraMap and will do so. Registration of the transformation routine must, of course, use the same name (and, in fact, be identical in most particulars) as was used in the original program which wrote the data.

This means that a set of co-operating programs which all have access to the same set of transformation routines and register them in identical fashion (see [*] for how this can best be achieved) can freely exchange data that contain IntraMaps. The need to avoid exporting such data to unsuspecting third parties ([*]) must, however, be re-iterated.


next up previous 264
Next: Managing Transformation Routines in Libraries
Up: Creating Your Own Private Mappings (IntraMaps)
Previous: Simplifying IntraMaps

AST A Library for Handling World Coordinate Systems in Astronomy
Starlink User Note 210
R.F. Warren-Smith & D.S. Berry
24th May 2011
E-mail:ussc@star.rl.ac.uk

Copyright (C) 2009 Science \& Technology Facilities Council