Ignore:
Timestamp:
06/21/12 15:00:20 (12 years ago)
Author:
Takeshi Nakazato
Message:

New Development: No

JIRA Issue: Yes CAS-4105

Ready for Test: Yes

Interface Changes: No

What Interface Changed: Please list interface changes

Test Programs: sdmath unit test

Put in Release Notes: No

Module(s): Module Names change impacts.

Description: Describe your changes here...

Unified behavior of scantable operation with scalar, 1-d array,
and 2-d array. Result of the operation (+,-,*,/) is returned as
new scantable. Returned scantable refers new table if sd.rcParamsinsitu?
is False while it refers the same table as input scantable if
sd.rcParamsinsitu? is True. For the later case, input scantable will
be modified. If sd.rcParamsscantable.storage? is 'disk', it means
that original scantable (on disk) will be modified so that those
functions must be used with care.

In task level (sdmath and sdscale), we take care to keep original table
unchanged so the users don't need to worry about that as long as they
are working on task level.


File:
1 edited

Legend:

Unmodified
Added
Removed
  • trunk/python/asapmath.py

    r2538 r2574  
    10221022             Otherwise, the array operation is done in-sitsu.
    10231023    """
     1024    if insitu is None: insitu = rcParams['insitu']
    10241025    nrow = scan.nrow()
    10251026    s = None
Note: See TracChangeset for help on using the changeset viewer.