Pc_align killed

[blye...@gmail.com]

Hi,

I am a begginer of ASP. I used pc_align tool to corret the CTX DEM from MOLA point datas. It seems the program was killed when it was trying to build the reference cloud tree. I have tired 2 version, including 2.62 and 2.70. Some CTX DEMs works well with the pc_align tool. Is there any requirements when trying to use pc_align tool to correct dem?

Here is the log file:

>>>>

 justin@justin-VirtualBox:~/DEM$ bash ~/scripts/asp_ctx_map_ba_pc_align2dem.sh -d stereodirs.lis -m 2500

Fri Apr 16 12:14:02 HKT 2021

Working on B17_016288_2131_J16_051100_2141

Running pc_align...

--> Setting number of processing threads to: 6

Writing log info to: dem_align/B17_016288_2131_J16_051100_2141_map_ba_align-log-pc_align-04-16-1214-24648.txt

Detected datum from B17_016288_2131_J16_051100_2141_map_ba-PC.tif:

Geodetic Datum --> Name: D_MARS  Spheroid: MARS  Semi-major axis: 3396190  Semi-minor axis: 3396190  Meridian: Reference Meridian at 0  Proj4 Str: +proj=sinu +lon_0=349.17461080875 +x_0=0 +y_0=0 +a=3396190 +b=3396190 +units=m +no_defs 

Will use datum (for CSV files): Geodetic Datum --> Name: D_MARS  Spheroid: MARS  Semi-major axis: 3396190  Semi-minor axis: 3396190  Meridian: Reference Meridian at 0  Proj4 Str: +a=3396190 +b=3396190

Computing the intersection of the bounding boxes of the reference and source points using 9000000 sample points.

Guessing file ../B17_016288_2131_J16_051100_2141_pedr.csv to be in latitude,longitude,height above datum (meters) format.

Reference box: (Origin: (-11.3712, 32.5111) width: 1.03989 height: 2.70312)

Source box:    (Origin: (348.624, 32.4514) width: 1.10417 height: 2.82075)

Intersection reference box:  (Origin: (-11.3712, 32.5111) width: 1.03989 height: 2.70312)

Intersection source    box:  (Origin: (348.629, 32.5111) width: 1.03989 height: 2.70312)

Intersection of bounding boxes took 43.2349 [s]

Reading: B17_016288_2131_J16_051100_2141_map_ba-PC.tif

        --> [********************************************************] Complete!

Too few points were loaded. Trying again.

        --> [********************************************************] Complete!

Loaded points: 96489709

Loading the reference point cloud took 164.948 [s]

Reading: ../B17_016288_2131_J16_051100_2141_pedr.csv

Guessing file ../B17_016288_2131_J16_051100_2141_pedr.csv to be in latitude,longitude,height above datum (meters) format.

Loaded points: 25562

Loading the source point cloud took 0.029231 [s]

Data shifted internally by subtracting: Vector3(2.76109e+06,-529884,1.88771e+06)

Building the reference cloud tree.

/home/justin/scripts/asp_ctx_map_ba_pc_align2dem.sh: line 83: 24648 Killed                  pc_align --num-iterations 2000 --threads 6 --max-displacement $maxd --highest-accuracy ${i}_map_ba-PC.tif ../${i}_pedr.csv -o dem_align/${i}_map_ba_align --datum D_MARS --save-inv-trans

--> Setting number of processing threads to: 6

File does not exist: B17_016288_2131_J16_051100_2141_map_ba_align-trans_reference.tif.

Thanks,
Justin

[Alexandrov, Oleg (ARC-TI)[KBR Wyle Services, LLC]]

The pc_align tool is a memory hog. You may want to get a machine with say 8 GB of RAM at least. Also the option  --highest-accuracy may be using more memory, if I recall right. 

Its manual page also specifies how to control how many reference points it reads, though fewer points may result in less accuracy, maybe. In your case it appears you loaded 96489709 points. 

You can also crop the input DEM to a smaller representative clip, get the alignment transform, then apply it by invoking the tool with the full DEM with 0 iterations and this obtained transform as the initial guess. (When it applies the transform it will apply it to every single point in the DEM, even though the transform was computed with a sample from a clip.)

---

From: ames-stereo-pi...@googlegroups.com <ames-stereo-pi...@googlegroups.com> on behalf of blye...@gmail.com <blye...@gmail.com>
Sent: Thursday, April 15, 2021 10:34 PM
To: Ames Stereo Pipeline Support <ames-stereo-pi...@googlegroups.com>
Subject: [EXTERNAL] Pc_align killed

 

--
You received this message because you are subscribed to the Google Groups "Ames Stereo Pipeline Support" group.
To unsubscribe from this group and stop receiving emails from it, send an email to ames-stereo-pipeline...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/ames-stereo-pipeline-support/bd49e472-2682-4d7c-834f-4c82d3bd0a91n%40googlegroups.com.

[blye...@gmail.com]

Thanks!! I will try using another machine with lagrer RAM. I removed the  -- highest-accuracy opition and it seems the pc_align can work with my DEM now.

Justin