Skip to main content

b4rpipe

License

Pipeline reduction tools for B4R/LMT data.


Installation


$ pip install b4rpipe

Usage


Reduce individual data

$ python
$ >>> import b4rpipe as Bp
$ >>> Bp.globBaseDir = '/home/hoge/b4r'
$ >>> Bp.globLogDir = '/home/hoge/b4r/logv1'
$ >>> Bp.PipelineAnalysis(86420)

This example shows a pipeline analysis for the data obsid 86420.

Reduce all data (for database)

$ python
$ >>> import b4rpipe as Bp
$ >>> Bp.globBaseDir = '/home/hoge/b4r'
$ >>> Bp.globLogDir = '/home/hoge/b4r/logv1'
$ >>> Bp.PipelineAnalysisBatchRun()

You need to specify following pathes.

b4pipe.globBaseDir

  • The path where "xffts" and "lmttpm" directorys are located.
  • XFFTS binary data (e.g., xffts20181003111006.xfftsx.01) should be stored under the "xffts" directory.
  • LMT antenna log data (e.g., lmttpm_2018-04-22_075858_01_0000.nc) should be stored under the "lmttpm" directory.

b4rpipe.globLogDir

  • The path where outputs are created.
  • Anywhere you like is OK.

Products


The script create following outputs (if possible).

  • Continuum Map Qlook (Pointing offset, efficiency (only for uranus), etc.)
  • Line (SiO) Map Qlook (Pointing offset, etc.)
  • Spectrum Qlook (with auto-flag)
  • Time series spectrum of PSW data (numpy readable format)
  • GoDec calibration results (see Taniguch et al. 2021)
  • MS2 (CASA readable format)

Data query and download (only for internal use now)


If you are in the NAOJ or IoA (U. Tokyo) local network, you can access the B4R ftp server.

$ python
$ >>> import b4rpipe as Bp
$ >>> Bp.PipelineAnalysis(86420,DataDownload=True,username='hogehoge',password='*****')

Then "rawdata" and "calibrated" directory appears at the current directory.

$ ls
raw calibrated
$ ls rawdata
lmttpm xffts
$ls calibrated
86420

Correspondence


  • B4R 2018/2019 (obsnum<=087433) data <-> CASA MS2
Name B4R CASA MS2
polarization A (correlation or stokes) YY
polarization B (correlation or stokes) XX
sideband LSB spw 0
sideband USB spw 1

Information


Metadata

Release files for b4rpipe 0.1.3

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Built distribution (wheel)

Table of built distributions (wheels) for b4rpipe 0.1.3
File Interpreter ABI Platform Actions
b4rpipe-0.1.3-py3-none-any.whl Python 3 none any Details for b4rpipe-0.1.3-py3-none-any.whl

Release files / b4rpipe-0.1.3-py3-none-any.whl

Download URL b4rpipe-0.1.3-py3-none-any.whl
Size 50.9 kB
Tags Python 3
SHA-256 checksum
How to use checksums
719ad119c0b150c30400bc162ac6556fc4798c88f7bf7b9d7b515531863e87f2
BLAKE2b-256 checksum
How to use checksums
8c25be124cedb496373549ac557bdc8bcba188f4530b34d10ff9849502eaf9db
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
No
Uploaded via twine/3.4.1 importlib_metadata/4.6.1 pkginfo/1.7.0 requests/2.25.1 requests-toolbelt/0.9.1 tqdm/4.61.2 CPython/3.8.10

Security for b4rpipe 0.1.3

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

No provenance found

None of the files in this release were uploaded with provenance metadata.

A note on package security

PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.

To learn more about protecting yourself from malicious actors, visit our package security documentation.

Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page