Multi-wavelength Data Analysis System User’s Guide,
Astronomy Data Center,
National Astronomical Observatory of Japan

17 October, 2023

Contents
1 Introduction
1.1 About the Multi-wavelength Data Analysis System . . . . . . . . . . . . . . . . . . . . . . . .
1.2 ADC open-use help desk . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1.3 Information about MDAS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

1
1
1
1

2 Regulations for use of Data Analysis System

3

3 How to get an MDAS user account
3.1 Application for MDAS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3.2 Application for VPN service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3.3 Application for group ID service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

5
5
5
5

4 How to use computers
4.1 How to use interactive data analysis servers . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.1.1 System conﬁguration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.1.2 How to log-in . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.1.3 Disk areas . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.1.4 Network access control . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.2 How to use batch processing data analysis servers . . . . . . . . . . . . . . . . . . . . . . . . .
4.2.1 System conﬁguration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.2.2 Queue conﬁguration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.2.3 Tutorial . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.2.4 PBS Professional . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.2.5 Handling of jobs in the maintenance . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.3 How to use the MDAS terminals . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.3.1 System conﬁguration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.3.2 How to log-in . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.3.3 Disk spaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.3.4 Network access control . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

7
7
7
8
8
9
10
10
11
11
12
18
19
19
19
19
20

5 Software conﬁguration
21
5.1 Software conﬁguration of the interactive/batch processing data analysis servers . . . . . . . . 21
5.2 How to use software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26
6 MDAS dedicated commands
35
6.1 How to use the MDAS dedicated commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35
6.1.1 lpall . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35
6.1.2 userinfo . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35
6.1.3 modify userinfo . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36
7 How to use peripherals
37
7.1 Network printers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37
7.1.1 List of network printers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37
7.1.2 How to use the network printers from the interactive data analysis servers . . . . . . . 37i

ii
8 How to use open-use rooms
39
8.1 About open-use rooms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39
8.2 How to use open-use linux terminals . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39
8.2.1 System conﬁguration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39
8.3 Software conﬁguration of the open-use linux terminals . . . . . . . . . . . . . . . . . . . . . . 40
8.3.1 How to login . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40
8.3.2 Disk areas . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40
8.3.3 Usage notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41
8.4 How to use open-use PCs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41
8.4.1 System conﬁguration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41
8.4.2 Software conﬁguration of the open-use PCs . . . . . . . . . . . . . . . . . . . . . . . . 41
8.4.3 How to use open-use PCs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43
8.5 How to use printers and scanners . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44
8.5.1 System conﬁguration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44
8.5.2 How to use the network printers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44
8.5.3 How to use large-format printers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44
8.5.4 How to use scanners . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45
8.6 Network connection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45
8.6.1 NAOJ network . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46
8.6.2 Internet . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46

1Chapter 1

Introduction
1.1

About the Multi-wavelength Data Analysis System

The Astronomy Data Center (ADC) is operating the Multi-wavelength Data Analysis System (MDAS) which
is an open-use computing system. MDAS is constructed to analyze astronomy data at various wavelengths.
There are over one hundred pieces of software and it supports data reduction and analysis of astronomy
data observed by various telescopes.
MDAS consists of computers and its peripherals. The computers are classiﬁed into interactive data
analysis servers, batch processing data analysis servers, and the MDAS terminals. Users access an interactive
data analysis server with SSH connection, and they can analyze data or submit jobs into a batch processing
data analysis server from the interactive data analysis server. The MDAS terminals located in the Subaru
building open-use room and ALMA building room 101 on the NAOJ Mitaka campus can be used forconnecting to the interactive data analysis servers.
MDAS is a computing system for “analytic researches of astronomical observation data”. For those whowant to perform calculations related to the simulation astronomy, please use computing systems oﬀered byCenter for Computational Astrophysics (http://www.cfca.nao.ac.jp).

1.2

ADC open-use help desk

The ADC open-use help desk is operating MDAS and supporting its users. If you have any questions about
MDAS or the open-use rooms, please feel free to contact us.
Place
Reception time
E-mail address
Extension number

1.3

ADC open-use help desk, 1F South building
Mon-Fri 9:30-12:00, 13:00-17:30
consult(at-mark)ana.nao.ac.jp3832

Information about MDAS

Please refer to the following URLs for information about MDAS.
• MDAS website (https://www.adc.nao.ac.jp/MDAS/mdas_e.html)• Information from ADC (https://www.adc.nao.ac.jp/cgi-bin/cfw2013/wiki.cgi/adcinfo/MLinfo)• FAQ (https://www.adc.nao.ac.jp/cgi-bin/cfw/wiki.cgi/FAQ/FAQE)

3Chapter 2

Regulations for use of Data Analysis
SystemNational Astronomical Observatory of Japan Astronomy Data Center Regulations for use of
Data Analysis System(Purpose)
The 1st article
This regulation intends to establish requirements about use of the data analysis system (hereafter“system”) in National Astronomical Observatory of Japan Astronomy Data Center (hereafter “center”)(User qualiﬁcation)
The 2nd article
The person who can use the system (hereafter “user”) is a member to whom the following applies:
1. Staﬀ of National Astronomical Observatory of Japan (hereafter NAOJ)
2. Researchers (who graduated from college) of astronomy and the related ﬁeld
3. The person who is allowed by the center chief in particular(The kind of use)
The 3rd article
The kind of use of the system is limited to the following.
1. Data processing of astronomy and related ﬁelds
2. The study and the work which are permitted by the center chief in particular(Use application)
The 4th article
The person who would like to use the system has to submit a prescribed application form to the center
chief and to receive an approval. When applying person belongs to the research institute outside Japan,
the research and educational staﬀ of NAOJ must be a supervisor of the applicant.
(Approval)
The 5th article
1. When the center chief accepts application form of the preceding article and admits to be suitable,
he approves it and gives the user a distinction sign (hereafter “user ID”) and also gives the group
distinction sign (hereafter “group ID”) if necessary.
2. The validity of user ID and group ID of the preceding clause is 1 year from approved use startingday. And it is available up until the next March 31.

4
3. When users hope to use their approved user ID or group ID continuously beyond the next March
31, they must renew the application within the period designated by the center chief.
(The prohibition of user ID diversion)
The 6th article
Users cannot use their user ID for the purpose other than that of application and users cannot allow
third party to use their user ID.
(The prohibition of group ID diversion)
The 7th article
Users cannot use their group ID for the purpose other than that of application and users cannot allow
third party except for their research group to use the group ID.
(Notiﬁcation)
The 8th article
When the following has occurred during the validity period of use, users should notify the center chief
promptly.
1. Use of system was ended or stopped.
2. Institution or position was changed.
(Revoke of use qualiﬁcation)
The 9th article
When users do not comply with the regulation of center or use the system except for the approved
purpose, the center chief can revoke the use qualiﬁcation or suspend the use.
(Final report)
The 10th article
When studies that related to the use of system have ﬁnished or the validity period of user ID has
ended, the center chief may ask users to submit reports on the system use (progress reports).
(The publication of results)
The 11th article
When users make public the results obtained by using the system, they must acknowledge clearly intheir papers the use of the system.
(Others)
The 12th article
1. Alteration and abolition of this regulation is executed by the center chief after consultation withthe technical committee.
2. In addition to this regulation, the center chief can establish a special bylaw about the system use
requirements.
(The rider)
1. This regulation comes into eﬀect on the March 1st 2013.

5

Chapter 3

How to get an MDAS user accountIn order to use MDAS, you must submit an application. By applying, your MDAS account will be issued
and you will be able to log-in to the interactive data analysis servers.
If a user’s PC is on the NAOJ network, then the user can access an interactive data analysis server
directly with SSH connection. In contrast, if a user’s PC is not on the NAOJ network, the user must
establish a Virtual Private Network (VPN) connection in advance. ADC also oﬀers VPN service for MDAS,
please submit an application for the VPN service if necessary.
MDAS provides group ID service. If you share data with other users, please submit an application for
the group ID service.

3.1

Application for MDAS

The application form of MDAS is on https://www.adc.nao.ac.jp/MDAS/appl/id_e.html. Please refer toregulations for use of MDAS (sea Section 2) before applying. Account registration process will be proceededout based on the information entered on the form. Once the registration process is complete, your accountwill be informed you by e-mail.

3.2

Application for VPN service

You can use the MDAS VPN service oﬀered by ADC or NAOJ staﬀ’s VPN service oﬀered by the NAOJ
NETWORK SERVICE HELP CENTER. If you are a NAOJ staﬀ, please use the NAOJ staﬀ’s VPN service.
If not, please use the MDAS VPN service.
An application form of the MDAS VPN service is on https://www.adc.nao.ac.jp/MDAS/appl/vpn_e.
html. Once the registration process is complete, how to use the MDAS VPN service will be informed you
by e-mail. Note that installation of anti virus software into user’s PC is mandatory for the use of the MDAS
VPN service. Be sure to install it. If you have any questions, please contact the ADC open-use help desk
(consult(at-mark)ana.nao.ac.jp).
An application form of the NAOJ staﬀ’s VPN service is on https://nethelp.mtk.nao.ac.jp/contents/
en/node/4. If you have any questions, please contact the NAOJ NETWORK SERVICE HELP CENTER(https://nethelp.mtk.nao.ac.jp/contents/en, accessible only from the NAOJ network).

3.3

Application for group ID service

A group ID is issued for a group of users. Files can be shared within the group of users by setting
the group ID as a group owner of the ﬁles. An application form of the group ID service is on https://www.adc.nao.ac.jp/MDAS/appl/gid_e.html.

7

Chapter 4

How to use computers
MDAS consists of interactive data analysis servers, batch processing data analysis servers, the MDAS
terminals, and its peripherals. In this chapter, we will introduce how to use each computer.

4.1

How to use interactive data analysis servers

Interactive data analysis servers are computers constructed for reducing and analyzing astronomy datainteractively. Each server is accessible from user’s PCs or the MDAS terminals in the open-use rooms with
SSH connection. For non-interactive and resource-intensive calculation, the batch data analysis servers
introduced in Section 4.2 should be used.

4.1.1

System conﬁguration

Interactive data analysis servers consist of 32 servers (FUJITSU Server PRIMERGY RX2530 M2). These
servers are classiﬁed into “kaim” servers and “kaih” servers from the diﬀerence of Random Access Memories(RAM) and Hard Disk Drives(HDD) they contain. A kaim server has 192GB RAM and 12TB HDD,
and a kaih server has 256GB RAM and 51TB HDD. The Red Hat Enterprise Linux 7 is installed into bothservers.
Table 4.1: Speciﬁcation of a kaim server
Host nameMachineQuantityOS
CPURAM
HDD of the local disk region
Size of the local disk region

kaim[01-20].ana.nao.ac.jp
FUJITSU Server PRIMERGY RX2530 M2
20
Red Hat Enterprise Linux 7Intel Xeon E5 2667 V4 3.2 GHz 16 core
DDR4 2400 RDIMM 192GB
1.8 TB 2.5 inch SAS 10000 rpm
12.24 TB

Table 4.2: Speciﬁcation of a kaih server
Host nameMachineQuantityOS
CPURAM
HDD of the local disk region
Size of the local disk region

kaih[01-12].ana.nao.ac.jp
FUJITSU Server PRIMERGY RX2530 M2
12
Red Hat Enterprise Linux 7Intel Xeon E5 2667 V4 3.2 GHz 16 core
DDR4 2400 RDIMM 256GB
10 TB 3.5 inch NLSAS 7200 rpm
51 TB

8

4.1.2

How to log-in

In order to log-in to an interactive data analysis server, the user’s PC must be connected to the NAOJ
network. To log-in to the server via the Internet, ﬁrst establish a VPN connection from the user’s PC to
the NAOJ network using either the MDAS VPN service or NAOJ staﬀ’s VPN service.
How to establish a VPN connection
MDAS VPN service The MDAS VPN service requires a VPN client software AnyConnect. Please
download and install it according to the e-mail you received after completing the registration process of the
VPN service.
In order to establish a VPN connection, launch the AnyConnect and connect to a VPN host server“kaimvpn.ana.nao.ac.jp” or “kaihvpn.ana.nao.ac.jp”. You should be required to input username and password, so please ﬁll in your MDAS account and password.
Note that you can log-in to the kaim and kaih server from both the “kaimvpn.ana.nao.ac.jp” and “kaihvpn.ana.nao.ac.jp”.
Table 4.3: MDAS VPN host server
Host namekaimvpn.ana.nao.ac.jp
kaihvpn.ana.nao.ac.jp

NAOJ staﬀ ’s VPN service
for details.

Please refer to https://nethelp.mtk.nao.ac.jp/contents/en/node/4

How to log-in to an interactive data analysis server
An user log-in to an interactive data analysis server “kaim[01-20].ana.nao.ac.jp” or “kaih[01-12].ana.nao.ac.jp”
with SSH connection1 . Please launch a terminal emulator on your PC and input commands as follows.
$ ssh [-X] your_account@(kaim[01-20]|kaih[01-12]).ana.nao.ac.jp


4.1.3



Disk areas

The following disk areas are available from the interactive data analysis servers.
Table 4.4: Disk areas available from the interactive data
analysis servers
Area
User home directory(NFS)
Large volume ﬁle system (NFS)
Local disk area of the
middle-range servers
Local disk area of thehigh-end servers

Mount point/home[0102]/lfs[01-16]

Size per a mount point
55TB

Soft/Hard limit
140GB/150GB

102TB

30TB・32TB

Retention period
As long as youraccount in force
12 months/wkm[01-20]

12TB

NA/NA

12 months/wkh[01-12]

51TB

14TB/16TB

12 months

1 Operation of the load balancer was terminated at the end of February 2023.

9
NFS areas for data migration
NFS areas for data migration/ext nfs[1-2]

393TB

9TB/10TB

NA/ext nfs3

306TB

9TB/10TB

NA• Before using the large volume ﬁle system or local disk area, please create a directory named youraccount under the disk areas.
• If your data volume reaches the soft/hard limit, application may not work normally.
• Files exceeding the retention period will be target of the periodic data deletion.
About NFS areas for data migration• These areas, which became available on 17th October 2022, are for placing user data that you want
to migrate to the next system. These areas will connect with the next system after the system
replacement.
• Please refrain from analyzing data on these areas.
• These areas can be accessed from kaim and kaih servers.
• Periodic data deletion will not be carried out for the time being.
Periodic data deletion Periodic data deletion will be carried out in the scheduled maintenance. The
policy of this deletion is as follows:• Target disk areas: the large volume ﬁle system and local disk areas exceeding utilization of 90%.
• Target ﬁles: ﬁles satisfying a condition that a diﬀerence between the date of the scheduled maintenanceand timestamp(ctime) of a ﬁle exceeds the retention period.
• Date on which the target disk areas are determined: 2 weeks before the scheduled maintenance.
• Date on which data deletion is carried out: scheduled maintenance day.
In a disk area, if disk usage exceeds utilization of 90% as of 2 weeks before the scheduled maintenance,then the disk area will be a target of the periodic data deletion. If disk usage does not exceed utilizationof 90%, then the disk area will not be a target. Files to be deleted are decided just before the scheduled
maintenance.
Disk quotas Disk quotas are set in MDAS to limit the amount of disk space used by each user. The
amount of maximum available disk space (soft limit/hard limit) varies for each disk area.
• Soft limit: amount of maximum available disk space. An user can write data to the disk area even if
the amount of data volume exceeds the soft limit. However, the user will become unavailable to write
after seven days if the situation persists.
• Hard limit: amount of absolute maximum available disk space. An user cannot write data to the disk
space if the amount of data volume exceeds the hard limit.
If your data volume reaches the soft/hard limit, application may not work normally, so you should copy or
remove your data before reaching.

4.1.4

Network access control

Access (i.e. ssh, scp, or rsync) from the interactive data analysis servers to devices on the NAOJ network
is not permitted for a security measure. In order to download data on an interactive data analysis server,
please execute commands such as “scp” or “rsync” from user’s PC to the interactive data analysis server.
$ scp your_account@(kaim[01-20]|kaih[01-12).ana.nao.ac.jp:<yourfile> ~/your/pc




10

4.2

How to use batch processing data analysis servers

Figure 4.1: Illustrated outline of batch processing data analysis servers.
MDAS has batch processing data analysis servers so as to implement batch processing. Batch processing
is a processing mechanism that computers automatically and sequentially process each job which is a groupof programs having shared purpose.
Processing eﬃciency may be decreased because of the lack of computational resource if multiple users run
multiple programs on a interactive data analysis server. A job management system on the batch processing
data analysis servers manages and runs these jobs sequentially, and the jobs should be processed mosteﬃciently in the usable computational resource. The batch processing data analysis servers are eﬀective
against many programs and programs which need big computational resource.
Batch servers consist of 2 servers (kaibm[01-02].ana.nao.ac.jp). A job management system, named PBS
Professional (hereinafter referred to PBS), is installed in the servers for the batch processing. The “kaibm01”
functions as a PBS management server, and both the “kaibm01” and “kaibm02” function as calculation
servers.
The PBS management server manages jobs submitted by users, and it allocates jobs to the calculation
servers. Submitted jobs will be queued when there is no calculation resource on the calculation servers.
Queued jobs will be run once computational resource is allocated. For the eﬃcient processing, it could well
happen that running jobs will be killed and required in order to run other jobs instead.

4.2.1

System conﬁguration

Batch processing data analysis servers consist of 2 servers (FUJITSU Server PRIMERGY RX2530 M2).
The Red Hat Enterprise Linux 7 is installed in each server.
Table 4.5: Speciﬁcation of a kaibm server
Host nameMachineQuantity
OS
CPU
RAM

kaibm[01-02].ana.nao.ac.jp
FUJITSU Server PRIMERGY RX2530 M2
2
Red Hat Enterprise Linux 7Intel Xeon E5 2667 V4 3.2 GHz 16 core
DDR4 2400 RDIMM 192GB

11

4.2.2

Queue conﬁguration

The PBS has job queues which control an execution sequence of jobs. When a user submits a job to one
of job queues, the PBS management server makes a judgment whether the calculation servers can executethe job or not. If it judges that they can execute the job, then the job will be run on them. If not, the job
will be queued up until the calculation resource is allocated. The usable computational resource and theexecution priority diﬀer by the job queues. Users must select a suitable queue depending on the scale of theuser’s own jobs because to use an unsuitable queue is a wasteful use of the computational resource.
Table 4.6: Job queue conﬁguration
Queue

CPU cores

q1
q4
q8
q16

1
4
8
16

Usable memory per a
job
11GB
44GB
88GB
176GB

Time limit for ajob
30 days
30 days
15 days
15 daysNumber of executablejobs per an user
hard limit:32, soft limit: 2
hard limit:8, soft limit: 1
hard limit:4, soft limit: 1
hard limit:2, soft limit: 1• The maximum number of submittable jobs by each user is 1024.
• The job priority is q1 >q4 >q8 >q16 >jobs lowered by soft limit.
• The hard limit is a number of maximum executable jobs. If an user submits multiple jobs exceeded
the hard limit value, a part of jobs will be queued.
• The soft limit is a number of jobs that will be executed preferentially. If an user submits multiple jobs
exceeded the soft limit value, a part of jobs will be low priority.
• Please refer to Section 4.2.4.7 for details of a priority control of jobs.

4.2.3

Tutorial

In order to use batch processing data analysis servers, you have to make a shell script called job script andsubmit a job into a job queue using “qsub” command from the “kaim” or “kaih” servers. In this section,
we will introduce basic steps to submit your jobs.
1. How to make a job script
2. How to submit and delete a job
3. How to display a job status
1. How to make a job script
Job script is a shell script in which the directives for the PBS and executable programs are described. The
following script is an example of the job script when we want to run a program “a.out” with a queue “q1”.
#!/bin/bash#PBS -M taro.tenmon@nao.ac.jp#PBS -m abe#PBS -q q1# Go to this job s working director
cd $PBS_O_WORKDIR# Run your executable./a.out
The “#PBS” lines are the directives for the PBS. In this script, we have made the following directives.

#PBS -M taro.tenmon@nao.ac.jp: E-mails will be sent to taro.tenmon@nao.ac.jp. Please make sure to
use this directive. If you do not use this directive, administrators will receive error E-mails bounced
back from the interactive server since the default E-mail address “user@host.ana.nao.ac.jp” is invalid.

12#PBS -m abe: An E-mail will be sent when a job is stopped, a job is started to run, and a job is ﬁnished,respectively. The “#PBS -m a” is enabled by default.
#PBS -q q1: A job will be submitted into the queue “q1”.
The “$PBS O WORKDIR” is an environment variable deﬁned in the PBS and expresses the path to thedirectory where the job script is submitted.
2. How to submit and delete a job
In order to submit a job into a queue, execute the “qsub” command on a interactive data analysis server.
$ qsub job_script.shThe submitted job can be deleted by executing the “qdel” command. The Job id can be displayed by using
the “qstat” command as we shall see later.
$ qdel job_id

3. How to display job status
The “qstat” command shows you a status of submitted jobs.
$ qstat
Job idName
UserTime Use S Queue---------------- --------- -------------- ----9013.a000
job1
user1
50:20:10 R q1
9019.a000
job2
user2
40:32:13 R q1
9030.a000
job3
user3
30:14:19 R q1
9079.a000
job4
user4
00:59:15 R q1
9102.a000
job5
user5
0 Q q1
Each column represents the job id, job name, user name, CPU time used, job status, and queue name,respectively. The job status has following states.
Q (Queued): Job is queued and will run once computational resource is allocated.
R (Running): Job is running.
S (Suspended): Job is suspended. It occurs when a higher priority job needs computational resource.
As a side note, ﬁnished jobs are shown by using a “qstat -x” command.

4.2.4

PBS Professional

In this section, we will introduce the PBS professional brieﬂy. Please refer to its User’s Guide(https://www.pbsworks.com/pdfs/PBSUserGuide18.2.pdf) for details. This section refers and quotes the User’s
Guide.
1. About the PBS Professional
2. Lifecycle of a PBS job
3. PBS job scripts
4. PBS commands
5. PBS directives
6. PBS environment variables
7. About a priority control of jobs
1. About the PBS Professional
PBS Professional is a distributed workload management system. PBS manages and monitors the computational workload for one or more computers. PBS does the following:13
Queuing jobs PBS collects jobs (work or tasks) to be run on one or more computers. Users submit jobs
to PBS, where they are queued up until PBS is ready to run them.
Scheduling jobs PBS selects which jobs to run, and when and where to run them, according to thepolicy speciﬁed by the site administrator. PBS allows the administrator to prioritize jobs and allocate
resources in a wide variety of ways, to maximize eﬃciency and/or throughput.
Monitoring jobs PBS tracks system resources, enforces usage policy, and reports usage. PBS tracks job
completion, ensuring that jobs run despite system outages.

2. Lifecycle of a PBS job
Your PBS job has the following lifecycle:
1. You write a job script.
2. You submit the job to PBS.
3. PBS accepts the job and returns a job ID to you.
4. The PBS scheduler ﬁnds the right place and time to run your job, and sends your job to the selected
execution host(s).
5. Licenses are obtained.
6. On each execution host, PBS creates a job-speciﬁc staging and execution directory.
7. PBS sets PBS JOBDIR and the job’s jobdir attribute to the path of the job’s staging and execution
directory.
8. On each execution host allocated to the job, PBS creates a job-speciﬁc temporary directory.
9. PBS sets the TMPDIR environment variable to the pathname of the temporary directory.
10. If any errors occur during directory creation or the setting of variables, the job is requeued.
11. Input ﬁles or directories are copied to the primary execution host.
12. The job runs under your login.
13. Output ﬁles or directories are copied to speciﬁed locations.
14. Temporary ﬁles and directories are cleaned up.
15. Licenses are returned to pool.

3. PBS job script
An PBS jobscript consist of a shebang to specify a shell, PBS directives, and job tasks(programs or commands). Under the Linux, a shell script, Python, Perl, or other script can be allowed to make a job script.
An example of job scripts using a shell script is as follows:#!/bin/sh# Job script with a single core
#PBS -M taro.tenmon@nao.ac.jp#PBS -m abe#PBS -q q1#PBS -r y#PBS -N job_name#PBS -o Log.out#PBS -e Log.err# Go to this job s working director
cd $PBS_O_WORKDIR# Run your executable./a.out




14




#!/bin/bash# Job script with multiple cores#PBS -M taro.tenmon@nao.ac.jp#PBS -m abe#PBS -r y#PBS -q q4#PBS -N job_name#PBS -o Log.out#PBS -e Log.err# Go to this job s working directory
cd $PBS_O_WORKDIR# Run your executable./a_0.out &./a_1.out

4. PBS commands

PBS has various commands so that users can submit, monitor, and manage jobs. We will describe commonlyused commands.

qsubThis is a command to submit a job into a queue. Please specify your job script for the argument.

$ qsub job_script.shqdel This is a command to delete a submitted job. The Job ID can be displayed by using “qstat” command
as we shall see later.
$ qdel Job_ID

qstat This is a command to check status of submitted jobs. Status of a speciﬁc job can be displayed by
specifying the Job ID as a argument. If a queue name is speciﬁed, status of the queue’s jobs should be
displayed.

15




$ qstat
Job id---------------1000.kaibm01
1001.kaibm01
1002.kaibm01
1003.kaibm01
1004.kaibm01

Name--------job1
job2
job3
job4
job5

User
-------user1
user1
user2
user2
user3

Time Use------50:20:10
40:32:13
30:14:19
00:59:15
0

S
R
R
R
R
Q

Queue
----q1
q1
q1
q4
q16

$ qstat 1000
Job id---------------1000.kaibm01

Name--------job1

User-------user1

Time Use------50:20:10

S
R

Queue
----q1$ qstat q1
Job idName
UserTime Use S Queue---------------- --------- -------------- ----1000.kaibm01
job1
user1
50:20:10 R q1
1001.kaibm01
job2
user1
40:32:13 R q1
1002.kaibm01
job3
user2
30:14:19 R q1
Each column represents the job id, job name, user name, CPU time used, job status, and queue name,respectively. The representative states of a job are as follows:
W (Waiting): Job is waiting. It will be queued and run when its submitter-assigned start time comes.
Q (Queued): Job is queued. Job will run once the calculation resource is allocated.
R (Running): Job is running.
S (Suspended): Job is suspended. It occurs when a higher priority job needs computational resource.
H (Held): Job is held. The “qhold” command can hold a job.
F (Finished): Job is ﬁnished. It represents that the job was completed, failed, or deleted.
The representative options of the “qstat” command are as follows:-a: Displays information for all queued and running jobs. You can check the elapsed time of a job.
-x: Displays information for ﬁnished jobs in addition to queued and running jobs.
-n: The exec host string is listed on the line below the basic information. If the -1 option is given, thecomment string is listed on the end of the same line.
-T: Displays the estimated start time for queued jobs
-f: Displays full information for jobs.
-Q: Displays queue status in default format.
-q: Displays queue status in alternate format.
qhold This is a command to hold a submitted job. The execution of the job is interrupted, and allocatedcomputational resource is released. The job will be resumed after executing “qrls” command that we shallsee later. This command is available if you would like to run queued or suspended jobs preferentially.
qrls This is a command to release a held job.


$ qrls Job_ID

5. PBS directives
PBS directives, which are used in a job script, are options for the “qsub” command to give various directives
to the PBS. A directive needs a preﬁx “#PBS” at the beginning of a line, and must be put above any
commands. If you put it below any commands, it will be ignored. We will show you representative PBS
directives.

16-M This directive sets an E-mail address. Please make sure to use this directive. If you do not use thisdirective, administrators will receive error E-mails bounced back from an interactive server since the default
E-mail address “user@host.ana.nao.ac.jp” is invalid.
#PBS -M your.address@example.jp-m This directive sets an E-mail notiﬁcation from the PBS. If you do not use this directive, “#PBS -ma” will be set.

#PBS -m n|(one or more of a,b,e)n: No mail is sent.
a: Mail is sent when the job is aborted by the PBS.
b: Mail is sent when the job begins execution.
e: Mail is sent when the job terminates.
-q This directive speciﬁes a queue where you submit a job. If you do not use this directive, “#PBS -q q1”
will be set.

#PBS -q q1|q4|q8|q16


q1: Job is submitted to the queue “q1”.
q4: Job is submitted to the queue “q4”.
q8: Job is submitted to the queue “q8”.
q16: Job is submitted to the queue “q16”.
-l This directive sets a limit on the calculation resource.
#PBS -l select=ncpus=X:mem=Ygb|walltime=hh:mm:ss

select=ncpus=X:mem=Ygb: The number of CPU cores and amount of memory used by your job are
restricted to X cores and Y GB, respectively. You cannot specify the number of CPU cores andamount of memory exceeded the default values for the queue you will use. Available units for the
memory are b, kb, mb, and gb.
walltime=hh:mm:ss: Maximum job execution time is set. You cannot specify the walltime exceeded thedefault value for the queue you will use.
-r This directive speciﬁes whether the PBS restarts submitted jobs or not after the system is restored. If
you do not use this directive, “#PBS -r -y” will be set.

#PBS -r y|ny: Job is rerunnable.
n: Job is not rerunnable.
-a This directive sets a job start time. The job will be waited, and submitted when the speciﬁed timecomes.
#PBS -a YYMMDDhhmm.SS

YYMMDDhhmm.SS: If you want to start a job at 07:30 on 1st September, 2020: “#PBS -a 2009010730.00”.

17-h This directive holds a job. The eﬀect is same as the “qhold” command.
#PBS -h-N This directive sets a job name. The speciﬁed name is displayed on the Name columns of the “qstat”
command. If you do not use this directive, the job name will be the job script’s ﬁle name.
#PBS -N Job_name-o This directive sets a ﬁle name to the standard output. If the relative path is used, the current directory
will be a directory where the “qsub” command was executed. If you do not use this directive, the ﬁle namewill be“(job script name).o(job ID)”, and stored into the directory where the “qsub” command is executed.#PBS -o /path/to/output.log
-e This directive sets a ﬁle name to the standard error output. If the relative path is used, the current
directory will be a directory where the “qsub” command was executed. If you do not use this directive, theﬁle name will be“(job script name).e(job ID)”, and stored into the directory where the “qsub” command is
executed.
#PBS -e /path/to/error.log
-j This directive merges a standard output and standard error output.
#PBS -j oe|eo

oe: Standard output and standard error output are merged into standard output.
eo: Standard output and standard error output are merged into standard error.
-R This directive removes the standard output and/or standard error output ﬁles.
#PBS -R o|e|oeo: The standard output stream is removed.
e: The standard error output stream is removed.
oe: The standard output and standard error output streams are removed.
6. PBS environment variables
PBS environment variables, which are deﬁned in the PBS, are available in the job script. Representative
variables are as follows:$PBS JOBID: Submitted job’s job ID.
$PBS JOBNAME: Submitted job’s job name.
$PBS O HOME: Value of environment variable $HOME.
$PBS O HOST: The host name on which the “qsub” command was executed.
$PBS O LANG: Value of environment variable $LANG.
$PBS O LOGNAME: Value of environment variable $LOGNAME.
$PBS O PATH: Value of environment variable $PATH.
$PBS O QUEUE: The queue name to which the job was submitted.
$PBS O SHELL: Value of environment variable $SHELL.
$PBS O WORKDIR: The absolute path of directory where “qsub” command was executed.

18
7. About a priority control of jobs
There are hard limit and soft limit on each queue which are values to limit on the number of executablejobs for each user.
The hard limit is a number of maximum executable jobs. If an user submits multiple jobs exceeded thehard limit value, a part of jobs will be queued. For example, if you submit ten jobs to q4 the hard limit ofwhich is eight, eight jobs will be executed but two jobs will be queued.
The soft limit is a number of jobs that will be executed preferentially. If an user submits multiple jobs
exceeded the soft limit value, a part of jobs will be low priority. For example, if you submit four jobs to q4
the soft limit of which is one, one job will be high priority but three jobs will be low priority lower than thatof q16 which has the lowest priority among queues on our system. When you or someone submits additionaljobs, the low priority jobs should be killed and requeued.
Examples of the priority control We show an example of the priority control in the situation where
several users submit jobs onto our system. In the example below, “1(AAAA)” represents a user A’s q4 job
which was ﬁrstly submitted onto the system. Note that the job priority is q1 >q4 >q8 >q16 >jobs loweredby soft limit and the soft limit values of q1, q4, q8, and q16 are 2, 1, 1, and 1, respectively.
1. User A submits six q4 jobs. All jobs will be run but the second and the following jobs will
be low priority due to the soft limit.
StatusJob
CPU Cores Used
Running(kaibm01) : 1(AAAA) 2(AAAA) 3(AAAA) 4(AAAA) 16/16
Running(kaibm02) : 5(AAAA) 6(AAAA)
8/16
Queued
:2. User B submits a q16 job. The q4 job in low priority and most recently submitted will bequeued.
StatusJob
CPU Cores Used
Running(kaibm01) : 1(AAAA) 2(AAAA) 3(AAAA) 4(AAAA) 16/16
Running(kaibm02) : 7(BBBBBBBBBBBBBBBB)
16/16
Queued: 5(AAAA) 6(AAAA)
3. User C submits two q1 jobs. The q4 job in low priority and most recently submitted will
be queued.
StatusJob
CPU Cores Used
Running(kaibm01) : 1(AAAA) 2(AAAA) 3(AAAA) 8(C) 9(C) 14/16
Running(kaibm02) : 7(BBBBBBBBBBBBBBBB)
16/16
Queued: 4(AAAA) 5(AAAA) 6(AAAA)
4. After ﬁrst to third jobs are ﬁnished, queued q4 jobs will be run.
StatusJob
CPU Cores Used
Running(kaibm01) : 4(AAAA) 5(AAAA) 6(AAAA) 8(C) 9(C) 14/16
Running(kaibm02) : 7(BBBBBBBBBBBBBBBB)
16/16
Queued
:4.2.5

Handling of jobs in the maintenanceFor the following reasons, if any system maintenance is planned, we recommend that you delete your jobs
before the maintenance and re-submit your jobs after the maintenance.
When batch processing data analysis servers are rebooted in a maintenance, running and queued jobs
will be killed, but will be re-submitted automatically after reboot. However, the re-submitting process
should be failed because the LDAP client is not started yet. This process is repeated 21 times, and you will
receive a lot of mails from PBS to inform you that your jobs are failed when you set a “PBS -m” option.
After that, jobs will be held by the system. The held jobs cannot be released with the general privilege, butuser can delete it.

19

4.3

How to use the MDAS terminals

The MDAS terminals2 are computers constructed for SSH connection to the interactive data analysis servers
and light processing. The large volume ﬁle system (/lfs[01-16]) and NFS areas for data migration (/ext
nfs[1-3]) are NFS mounted, so that data can be downloaded to the terminals eﬃciently.

4.3.1

System conﬁguration

The MDAS terminals consist of 10 computers located in the Subaru building open-use room (sbt[0110].ana.nao.ac.jp) and 8 computers located in the ALMA building room 101 (alt[01-08].ana.nao.ac.jp).
There are desktop PCs and compact PCs in each room. The Rocky Linux 9 is installed as the Operating
System.
Table 4.7: Speciﬁcation of the MDAS terminals(desktop
PC)
Host nameMachineQuantity
OS
CPU
RAM

sbt([01-05]—alt[01-05).ana.nao.ac.jp
DELL Precision 3650
10Rocky Linux 9Intel Xeon E5 W-1950 3.3 GHz 6 core
DDR4-3200 RDIMM 16GB

Table 4.8: Speciﬁcation of the MDAS terminals(compact
PC)
Host nameMachineQuantity
OS
CPU
RAM

4.3.2

(sbt[06-10]—alt[06-08]).ana.nao.ac.jp
Minisforum UM580B
8
Rocky Linux 9
AMD Ryzen 7 5800H 8C/16T 3.2GHz
DDR4-3200 DIMM 16GB

How to log-in

The MDAS terminals require the MDAS account. The login steps are as follows.
1. Input your account into the username ﬁeld.
2. After that, input your password into the password ﬁeld.

4.3.3

Disk spaces

The following disk areas are available from the MDAS terminals.
Table 4.9: Disk areas available from the MDAS terminals
Area
Large volume ﬁle system (NFS)

Mount point/lfs[01-16]

Size per a mount point
102TB

Soft/Hard limit
30TB/32TB

2 Operation of the terminal workstations was terminated at the end of February 2023.

Retention period
12 months

20
NFS areas for data migration
NFS areas for data migration/ext nfs[1-2]

393TB

9TB/10TB

NA/ext nfs3

306TB

9TB/10TB

NA• In the MDAS terminals, user home directories are created for each terminal. User home directories(NFS) accessible from the interactive data analysis servers are not mounted.
• Before using the large volume ﬁle system or local disk area, please create a directory named youraccount under the disk areas.
• If your data volume reaches the soft/hard limit, application may not work normally (refer to Section
4.1.3 (Disk quotas) for details).
• Files exceeding the retention period will be target of the periodic data deletion (refer to Section 4.1.3(Periodic data deletion) for details).

4.3.4

Network access control

SSH connection to the MDAS terminals is not permitted for a security measure. Access (i.e. ssh, scp, or
rsync) from the terminals to devices on the NAOJ network is not permitted, either.

21

Chapter 5

Software conﬁguration
5.1

Software conﬁguration of the interactive/batch processing data
analysis servers
Table 5.1: Operating system

Operating system
Red Hat Enterprise Linux 7

Hostkaim[01-20], kaih[01-12], kaibm[01-02]

Table 5.2: Development environment
Softwarekterm
mlterm
rxvt
xterm
awk
make
patch
sed
tar
bzip2
gzip
less
lz4

Version
6.2.0
3.8.4
2.7.10
7.6.0
4.0.2
3.82
2.7.1
4.2.2
1.26
1.0.6
1.5
458
1.7.3

Notes

Table 5.3: Web browser
SoftwareGoogle Chrome
Firefox

VersionLatest Ver.
latest version

Notes

22
Table 5.4: Word processing and Japanese input system
Softwareemacs
xemacs
nvi
vim
latex
platex
TeX Livebibtex
pandocpdvipsa2ps
ghostview
ghostscript
anthy
canna
freewnn
nkf
skk

Version22.3, 24.3
21.5.34
1.79
7.4
3.14159265
3.14159265
2017
0.99d
–
5.997
4.14
3.7.4
9.07
9100h
3.7
1.1.1-a023
2.1.3
16.1

Notes

Notes: Section 5.2.11.

Table 5.5: Video and image processing software
Softwareevince
tgif
xﬁg
gimp
ImageMagick
netpbmmpeg play
mpeg encode

Version
3.14.24.2.2
3.2.5
2.8.166.7.8.9
10.61.02
2.4
1.5c

Notes

Table 5.6: Programming language
Softwarecpanm
devtoolset-11
GCC(incl. g77)
GCC
gdb
Java SE Development Kit
Intel oneAPI
pdl
perl
php
pythonVersion1.6922
–
3.4.6
4.8.5
7.6.1
1.8.0
2023.0.0
2.019
5.16.35.4.162.7.14
3.5.4

Notes

End of support: 30 November 2020

How to start: python or python2 or python2.7
How to start: python3.5

23
3.8.3
astropycosmolopy
dustmaps
healpyipythonmatplotlib
numpy
pandasPmw
pymultinest
pyraf
pyregion
pyspecKit
requestsrpy2
scipy
seaborn
urwid

2.0.3
0.1.104
0.1a12
1.11.05.5.0
2.1.1
1.13.30.21.1
2.0.1
2.6
2.1.142.0
0.1.21
2.18.4
2.8.6
1.0.0
0.9.0
2.0.1

astropy
dustmaps
healpyipythonjupyter
matplotlib
numpy
pandasPmw
pymultinest
pyqtgraph
PyQt5
pyraf
pyregion
pyspecKit
requestsrpy2
scipy
seaborn
urwid

2.0.3
0.1a12
1.11.0
6.2.1
1.0.0
2.1.1
1.13.30.21.1
2.0.1
2.6
0.10.05.14.02.1.142.0
0.1.21
2.18.4
2.9.1
1.0.0
0.9.0
2.0.1

APLpy
astropy
dustmaps
healpyipythonjupyter
matplotlib
numpy
pandasPmw
pymultinest
pyqtgraph

2.0.3
4.0.1.post1
1.0.4
1.13.07.16.1
1.0.0
3.2.2
1.18.5
1.0.5
2.0.1
2.9
0.11.0How to start: python3 or python3.8
Modules for Python2.7

How to start: ipython or ipython2

Modules for Python3.5

How to start: /usr/local/python/3.5/bin/ipython
Notes: Section 5.2.7.

Modules for Python3.8

How to start: ipython3
Notes: Section 5.2.7.

24
PyQt5
pyraf
pyregion
pyspecKit
requestsrpy2
scipy
seaborn
stsci.tools
urwid

5.15.02.1.152.0
0.1.232.24.03.3.5
1.5.1
0.10.1
3.6.0
2.0.1

r
ruby
tcl/tk
bash
tcsh

3.4.3
2.0.0p648
8.5.134.1.466.18.01

Table 5.7: Astronomy and science software
Softwareaips
Astrometry.net
CARTA

CASA

Version
31DEC17
31DEC190.73
1.1, 1.2.1, 1.3,
1.4,
2.0,
3.0,
4.0beta, 4.0
6.6.0(Python3.8)

Notes
How to use: Section 5.2.1.

How to start: Section 5.2.15

How to start: casa (Don’t use CASA on the /lfs[01-16].
See Section 5.2.2.)

25

CASA Analysis
Utilities
CDSclient
COMICS q series
difmap
DisPerSE
ds9
FITSIO/CFITSIO
fv
getsf
GILDAS
gnuplot
gsl
HEALPix Facility
HEAsoft
HyperZIDLIDL Astronomy
User’s Library
IRAF

Java NewStar

4.7.0-1,
4.7.1, How to start: Section 5.2.2.
4.7.2, 5.0.0, 5.1.0,
5.1.1, 5.1.2, 5.3.0,
5.4.0, 5.4.1, 5.5.0,
5.6.1(pipeline),
5.6.2,
5.7.0,
5.7.2, 5.8.0, 6.1.0,
6.1.1(pipeline),
6.1.2(pipeline),
6.2.0,
6.2.1(pipeline),
6.3.0,
6.4.0(Python3.6),
6.4.0(Python3.8),
6.4.1(pipeline),
6.4.3(Python3.6),
6.4.3(Python3.8),
6.4.4(Python3.6),
6.4.4(Python3.8),
6.5.0(Python3.6),
6.5.0(Python3.8),
6.5.1(Python(3.6),
6.5.1(Python(3.8),
6.5.2(Python3.6),
6.5.2(Python3.8),
6.5.3(Python3.6),
6.5.3(Python3.8),
6.5.4(pipeline),
6.5.5(Python3.6),
6.5.5(Python3.8),
6.5.6(Python3.8),
6.6.0(Python3.8)
1.3845
How to use: Section 5.2.3
3.84
4.2
2.5e
0.9.248.1
3.48
5.4220530dec17a
5.2.8
1.15
3.82
6.22.1
1.1
8.8.1
27-Feb-2020
2.14.1
2.16.12.17
20171120

How to start: Section 5.2.4.

Installed in: /usr/local/Healpix 3.82

29 licenses available. Can’t start IDL: Section 5.2.5.

How to start: Section 5.2.6.

26
Karma
Mathematica
MCSMDPMCSREDMCSRED2MIDASMIRIAD
Montage
MSCRED
MultiNest
NewStarNOSTARPBS Professional
Pgplot/Cpgplot
PgperlScamp
SDFRED
SExtractor
SkyCatstarﬁnder
STSDASSWarp
TABLESVEDA
WCSTools
XPA
x11iraf

5.2

1.7.2513.0.1
1.1.3
2016112520171125
17FEBpl1.2
4.3.8
5.0
5.05
3.1
20150422
20120528
2021.1.2
5.2.2
2.21
2.0.4
1.4.1
2.0.1
2.19.5
3.1.3
1.8.2
3.17
2.38.0
3.17–
3.9.6
2.1.172.0beta

Notes: Section 5.2.14.
2 licenses available.
How to start: Section 5.2.8.
Requirements: IRAF>2.16
How to start: Section 5.2.9
Only available on IRAF 2.16.1
Can’t start NewStar: Section 5.2.10
Software for batch system

How to use softwareThis section introduces the software that requires attention when using it.
1. AIPS
2. CASA
3. CASA Analysis Utilities
4. GILDAS
5. IDL6. IRAF
7. Jupyter Notebook
8. MCSRED
9. Miriad
10. NEWSTAR
11. pLaTeX
12. SDFRED
13. xdvi
14. Karma
15. CARTA

1. AIPS
Application For those who want to use AIPS, please inform us (consult(at-mark)ana.nao.ac.jp) of your
MDAS account. We will allocate an AIPS ID to each user. AIPS users can only use their own allocated27
AIPS ID, but cannot use other user’s AIPS ID.
If you do not have allocated AIPS IDs, only AIPS IDs between 2 and 9 can be used. Anyone can use
these IDs, so someone may handle your data. We recommend that you get allocated AIPS IDs.
Data storage location The AIPS user data directory is set up in the home directory as AIPS IDs areallocated. Since the home directory is NFS, you can access same data from any interactive data analysis
servers.
If you do not have allocated AIPS IDs, AIPS user data is stored into “/lfs01/aips/DATA/LOCALHOST
1”. Since /lfs01 is a target of the periodic data deletion, the AIPS user data would be deleted.
How to start AIPS

Please input commands below. AIPS(31DEC19) should be started.

$ source /usr/local/aips/LOGIN.SH$ aips tv=local:0
If you want to use old versions, please execute following script by using a source command (bash).
31DEC17: /usr/local/aips-31DEC17/LOGIN.SH

2. CASA
Don’t use CASA on disks that are NFS mounted (/lfs[01-16:) We strongly recommend that you
use CASA on the home or local disk areas (/wkm[01-20], wkh[01-12]) because if you use CASA on disksthat are NFS mounted (/lfs[01-16]), all tasks could not be run normally with all versions of CASA.
How to start CASA The default path of CASA is set to latest version basically. If you want to use oldversions, please execute following lines.
4.7.0-1: /usr/local/casa/casa-release-4.7.0-1-el7/bin/casa
4.7.1: /usr/local/casa/casa-release-4.7.1-el7/bin/casa
4.7.2: /usr/local/casa/casa-release-4.7.2-el7/bin/casa
5.0.0: /usr/local/casa/casa-release-5.0.0-218.el7/bin/casa
5.1.0: /usr/local/casa/casa-release-5.1.0-74.el7/bin/casa
5.1.1: /usr/local/casa/casa-release-5.1.1-5.el7/bin/casa
5.1.2: /usr/local/casa/casa-release-5.1.2-4.el7/bin/casa
5.3.0: /usr/local/casa/casa-release-5.3.0-143.el7/bin/casa
5.4.0: /usr/local/casa/casa-release-5.4.0-70.el7/bin/casa
5.4.1: /usr/local/casa/casa-release-5.4.1-32.el7/bin/casa
5.5.0: /usr/local/casa/casa-release-5.5.0-149.el7/bin/casa
5.6.1(pipeline): /usr/local/casa/casa-pipeline-release-5.6.1-8.el7/bin/casa
5.6.2(pipeline): /usr/local/casa/casa-pipeline-release-5.6.2-2.el7/bin/casa
5.7.0: /usr/local/casa/casa-release-5.7.0-134.el7/bin/casa
5.7.2: /usr/local/casa/casa-release-5.7.2-4.el7/bin/casa
5.8.0: /usr/local/casa/casa-release-5.8.0-109.el7/bin/casa
6.1.0: /usr/local/casa/casa-6.1.0-118/bin/casa
6.1.1(pipeline): /usr/local/casa/casa-6.1.1-15-pipeline-2020.1.0.40/bin/casa

28
6.1.2(pipeline): /usr/local/casa/casa-6.1.2-7-pipeline-2020.1.0.36/bin/casa
6.2.0: /usr/local/casa/casa-6.2.0-124/bin/casa
6.2.1: /usr/local/casa/casa-6.2.1-7-pipeline-2021.2.0.128/bin/casa
6.3.0: /usr/local/casa/casa-6.3.0-48/bin/casa
6.4.0(Python3.6): /usr/local/casa/casa-6.4.0-16-py3.6/bin/casa
6.4.1(pipeline): /usr/local/casa/casa-6.4.1-12-pipeline-2022.2.0.64/bin/casa
6.4.1(pipeline): /usr/local/casa/casa-6.4.1-12-pipeline-2022.2.0.68/bin/casa
6.4.0(Python3.8): /usr/local/casa/casa-6.4.0-16-py3.8/bin/casa
6.4.3(Python3.6): /usr/local/casa/casa-6.4.3-27-py3.6/bin/casa
6.4.3(Python3.8): /usr/local/casa/casa-6.4.3-27-py3.8/bin/casa
6.4.3(Python3.6): /usr/local/casa/casa-6.4.4-31-py3.6/bin/casa
6.4.3(Python3.8): /usr/local/casa/casa-6.4.4-31-py3.8/bin/casa
6.5.0(Python3.6): /usr/local/casa/casa-6.5.0-15-py3.6/bin/casa
6.5.0(Python3.8): /usr/local/casa/casa-6.5.0-15-py3.8/bin/casa
6.5.1(Python3.6): /usr/local/casa/casa-6.5.1-23-py3.6/bin/casa
6.5.1(Python3.8): /usr/local/casa/casa-6.5.1-23-py3.8/bin/casa
6.5.2(Python3.6): /usr/local/casa/casa-6.5.2-26-py3.6/bin/casa
6.5.2(Python3.8): /usr/local/casa/casa-6.5.2-26-py3.8/bin/casa
6.5.3(Python3.6): /usr/local/casa/casa-6.5.3-28-py3.6/bin/casa
6.5.3(Python3.8): /usr/local/casa/casa-6.5.3-28-py3.8/bin/casa
6.5.4(pipeline): /usr/local/casa/casa-6.5.4-9-pipeline-2023.1.0.124/bin/casa
6.5.5(Python3.6): /usr/local/casa/casa-6.5.5-21-py3.6/bin/casa
6.5.5(Python3.8): /usr/local/casa/casa-6.5.5-21-py3.8/bin/casa
6.5.6(Python3.8): /usr/local/casa/casa-6.5.6-22-py3.8.el7/bin/casa
6.6.0(Python3.8): /usr/local/casa/casa-6.6.0-20-py3.8.el7/bin/casa

3. CASA Analysis Utilities
How to use CASA Analysis Utilities are installed in the following path: “/usr/local/src/casa/analysis
scripts/”. Edit your casapy initializing ﬁle “˜/.casa/init.py” or create new ﬁle if it does not exist, and add
the following.

import sys
aupath = ’/usr/local/src/casa/analysis_scripts’
if aupath not in sys.path:
sys.path.append(aupath)import analysisUtils as aU




29
checked functions

Operation of function on the following web site was conﬁrmed.

Analysis Utilities in CASA Guide (https://casaguides.nrao.edu/index.php/Analysis_Utilities)
Note following points:• Functions of plotbandpass and plotweather are not conﬁrmed because these functions are included in
CASA. Use the CASA tasks of the same name.
• The following function was found not to work properly in some cases.
– obslist: It does not work properly when antenna ID is set for parameter cofa.
– plotWVRSolutions: Error when ﬁeld is set by ID or name.
– timeOnSource: Probably return incorrect results for mosaic observation data.

About Antenna Pad Information
require it can not work properly.

Because antenna pad information is not installed, functions that

When you install into your home directory You can install CASA Analysis Utilities also into yourhome directory. In that case, deploy the tools referring to the following site and change the path describedin the init.py to the appropriate one.
Analysis Utilities in CASA Guide (https://casaguides.nrao.edu/index.php/Analysis_Utilities)

4. GILDAS
How to start GILDAS You need to input the following command before starting the GILDAS.
$ gilenv
After executing the command, you should be able to start the GILDAS only on the terminal emulator.



5. IDL
Can’t start IDL (1) After you kill IDL forcibly, you may have a trouble to restart IDL. The IDL
conﬁguration ﬁles may be damaged due to the forced termination. You may solve the problem with thefollowing operation. However, the conﬁguration ﬁle will be lost, and the IDL environment will be initialized.
Rename "~/IDLWorkspace8?"
Rename "~/.idl"

Can’t start IDL (2) If you change the shell after you log-in to the MDAS, you cannot start the IDL
because IDL cannot read conﬁguration ﬁles. Please use a following command if you want to change theshell.
$ modify_userinfo -s [Shell]

6. IRAFHow to start IRAF 2.14 The default path is IRAF 2.16. If you want to use IRAF 2.14, please append
following lines into your conﬁguration ﬁles.



30




[sh, bash]
Append following script to both "~/.bashrc" and "~/.bash_profile".
if [ -r /usr/local/iraf2141/iraf/unix/hlib/setup.sh ]; thenexport IRAFARCH=redhat
export iraf=/usr/local/iraf2141/iraf/. $iraf/unix/hlib/setup.shfi[csh, tcsh]
Append following script to "~/.cshrc".
if ( -r /usr/local/iraf2141/iraf/unix/hlib/setup.csh ) thensetenv IRAFARCH redhat
setenv iraf /usr/local/iraf2141/iraf/
source $iraf/unix/hlib/setup.csh
endif




How to start IRAF 2.17




If you want to use IRAF 2.17, please execute the following command ﬁrst.

[sh, bash]
source /usr/local/iraf217/iraf.sh[csh, tcsh]
source /usr/local/iraf217/iraf.csh

7. Jupyter Notebook
When you launch the jupyter notebook with “–no-browser” option on the interactive data analysis servers
and use the notebook from the user’s PC on the NAOJ network, we strongly recommend to use the SSH
port forwarding because the communication between the user’s PC and the server is not encrypted.
If you use the MDAS vpn service, the SSH port forwarding is not required because the VPN encrypts
the communication.
How to use the SSH port forwarding for Jupyter Notebook
1. Launch the jupyter notebook on the interactive data analysis server with “–no-browser” option.
$ jupyter notebook --no-browser--> URL to access the notebook is displayed.
e.g.: http://localhost:8888/?token=...

2. Execute SSH connection from the user’s PC .
$ ssh -L 8888:localhost:8888



your_account@server_name(executing jupyter)

Note: If the port number in the URL differs from 8888,
match the number in SSH option to the port number.

3. Launch a web browser on user’s PC, enter the URL in address bar, and access the URL.



31

8. MCSRED
How to start the MCSRED When the mcsred is loaded from the IRAF, the MCSRED2 will be started
by default. Those who want to use the MCSRED need to modify the following ﬁles.
<modification of the login.cl>task $mcsred=/usr/local/subaru/MCSRED/mcsred.cl
set dir_mcsred="/usr/local/subaru/MCSRED/"






<modification of the sh/csh setting files>[sh, bash]
Add the following line into the ~/.bashrc and ~/.bash_profile.
export MCSRED_DIR=/usr/local/subaru/MCSRED[csh, tcsh]
Add the following line into ~/.cshrc.
setenv MCSRED_DIR /usr/local/subaru/MCSRED

9. Miriad
How to use Miriad The following list is aliases of the Miriad environment setting scripts for eachtelescope. You need to call one of the following aliases before starting the Miriad.
[sh, bash]
alias mirenv="source /usr/local/miriad/miriad_start.sh" (for CARMA)
alias mirenv-sma="source /usr/local/miriad/miriad-sma/lib/miriad/automiriad.sh"(for SMA)
alias mirenv-ata="source /usr/local/miriad/miriad-ata/lib/miriad/automiriad.sh"(for ATA)
alias mirenv-bima="source /usr/local/miriad/miriad-bima/lib/miriad/automiriad.sh"(for BIMA)
alias mirenv-gmrt="source /usr/local/miriad/miriad-gmrt/lib/miriad/automiriad.sh"(for GMRT)
alias mirenv-wsrt="source /usr/local/miriad/miriad-wsrt/lib/miriad/automiriad.sh"(for WSRT)
alias mirenv-atnf="source /usr/local/miriad/miriad-atnf/miriad/MIRRC.sh" (for ATNF)
alias mirenv-atnf2="source /usr/local/miriad/miriad-atnf2/lib/miriad/automiriad.sh"(for ATNF, old version)
alias mirenv-fasr="source /usr/local/miriad/miriad-fasr/miriad_start.sh" (for FASR)
alias mirenv-lofar="source /usr/local/miriad/miriad-lofar/miriad_start.sh" (for LOFAR)[Example: to start Miriad for SMA]
$ mirenv-sma$ miriad• If you call an unsuitable alias, the Miriad would output incorrect results.
• We have prepared two ATNF aliases because a part of tasks did not work in the old version. If you
want to use old the version, please call the “mirenv-atnf2”.

10. NEWSTAR
Can’t start NEWSTAR If empty temporary ﬁles such as “nsmmmlock”, “mmm*”, “pops*”, “AIPS*”,and “ttt*” exist in your home directory, then you can’t open a login window or “AIPS can’t start” would be
displayed after you push a “ok” in the login window of the NEWSTAR. You can start NEWSTER normally32
after removing the temporary ﬁles.

11. pLaTeX
Compilation error There is a case where EUC-JP LaTeX ﬁles can not be compiled using pLaTeX. The
default character code of the LaTeX installed in the MDAS is UTF-8, so if you want to compile a EUC-JP
LaTeX ﬁle, please use -kanji option.
$ platex -kanji=euc hoge.tex


12. SDFRED
How to start SDFRED The default path of the SDFRED is a latest version. If you want to use
SDFRED 1.4.1, please append following lines into your conﬁguration ﬁles.
[sh, bash]
1) Append the following lines to both "~/.bashrc" and "~/.bash_profile".
PATH=/usr/local/subaru/sdfred20100528/bin:$PATH export PATH
export PATH
2) Execute "source /.bashrc"[csh, tcsh]
1)Append the following line to "~/.cshrcf".
set path=(/usr/local/subaru/sdfred20100528/bin $path)2) Execute "source ~/.cshrc".
3) Execute "rehash".


13. xdvi
Text garbling Files compiled with EUC-JP would be garbled by xdvi. Please use -kanji option if you
compile EUC-JP ﬁles.
$ platex -kanji=euc hoge.tex


14. Karma
Environment settingYou need to execute the following command before starting Karma.

[sh, bash]$ source /usr/local/karma/.karmarc[csh, tcsh]$ source /usr/local/karma/.login
(Notice) The reference of the “convert” command will be changed from “/usr/bin/convert” to “/usr/l
ocal/karma/bin/convert” after executing the command above. Please check a full-path of the “convert”
command if you use “/usr/bin/convert”.

15. CARTA
How to start CARTA Please follow the steps below when you use CARTA 2.0 or later. It may not be
started by the “carta” command alone.

33




(1) Start CARTA with ‘‘no browser’’ option.
$ carta --no_browser &(2) Start any browser on user’s PC.
(3) The following message is displayed in step (1).
[info] CARTA is accessible at [http://...]
Copy the URL and paste it into the browser.
CARTA starts when you open the link.
The default path of CARTA is set to latest version basically. If you want to use old versions, please execute
following lines.
【1.1】/usr/local/carta/CARTA-v1.1-RedHat7.AppImage【1.2.1】/usr/local/carta/CARTA-v1.2.1.AppImage【1.3】/usr/local/carta/CARTA-v1.3.AppImage【1.4】/usr/local/carta/CARTA-v1.4.AppImage【2.0】/usr/local/carta/CARTA-v2.0-redhat.AppImage【3.0】/usr/local/carta/carta-3.0-x86 64.AppImage【4.0beta】/usr/local/carta/carta-v4.0.0-beta.1-x86 64.AppImage【4.0】/usr/local/carta/carta-4.0-x86 64.AppImage

35

Chapter 6

MDAS dedicated commands
6.1

How to use the MDAS dedicated commands

The following commands are available on MDAS.
Table 6.1: List of unique commands
Commandlpall
userinfo
hline modify userinfo

6.1.1

OutlineOutput ﬁles to a printer
Display user information
Modify user information

lpall

The lpall command makes it easy to print single and double-sided PS, PDF and text ﬁles.




Usage
$ lpall -d <printer_name> [-L|-K] <file_name>
Option-d: Specify a printer (nwp-m1,nwp-sb,nwp-al). The following printers are available:
nwp-m1 (South building open-use room B)
nwp-sb (Subaru building open-use room)
nwp-al (ALMA building room 101)
-L: Double-sided printing (long edge binding)-K: Double-sided printing (short edge binding)
Example$ lpall -d nwp-m1 test.ps# Single-sided printing of test.ps with nwp-m1$ lpall -d nwp-m1 -L test.pdf# Double-sided printing (long edge binding) of test.pdf with nwp-m1• This command automatically identiﬁes the type of input ﬁle by the contents of the ﬁle, not by its
extension.
• If the “-d” option is omitted, data is output to the default printer(see Section 7.1.2).

6.1.2

userinfo

The userinfo command displays the current login shell(default shell is bash), registered e-mail address, andname(GECOS). This command requires your MDAS password.

36




Usage
$ userinfo
Example$ userinfo
Enter LDAP Password:
loginshell: /bin/bash
mail: your_account@nao.ac.jp
gecos: Your Name




6.1.3

modify userinfo

The modify userinfo command can be used to modify your MDAS password, registered e-mail address, andcurrent login shell.


Usage
$ modify_userinfo (-h|-p|-m <your_e-mail_address>|-s <login_shell>|-v)
Option-h Display help message and exit
-p Modify the password-m Modify the e-mail address-s Modify the current login shell. The following shells are available:/bin/bash (/usr/local/bin/bash)/bin/tcsh (/usr/local/bin/tcsh)/bin/csh/bin/ksh/bin/sh/bin/zsh (/usr/local/bin/zsh)-v Display version information and exit
Set up your password according to the following policy. Users who wish to reset their passwords need tocontact us ((consult(at-mark)ana.nao.ac.jp).

Password policy:
The password shall be a combination of 2 types or more of English lowercase
letters, English uppercase letters, numbers, and symbols, and it must be of thelength of 12 characters or more.




37

Chapter 7

How to use peripherals
This section introduces the peripherals available on MDAS.

7.1

Network printers

7.1.1

List of network printers

There are network printers(Fujiﬁlm ApeosPrint C5240) in the South building open-use room B, Subaru
building open-use room, and the ALMA building room 101. A4-size print outs can be made from theinteractive data analysis servers.
Note that operation of the A3/A4 printers, Fuji Xerox Docuprint C5000 d, was terminated at the endof February, 2023.
Table 7.1: List of network printers
Host namenwp-m1.ana.nao.ac.jp
nwp-sb.ana.nao.ac.jp
nwp-al.ana.nao.ac.jp

7.1.2

IP address
133.40.130.137
133.40.130.139
133.40.130.140

Place
South building open-use room B
Subaru building open-use room
ALMA building room 101

How to use the network printers from the interactive data analysis servers

Data can be output from the interactive data analysis servers to the printers(Table 7.1). The following
printers are set as default output destinations.
Table 7.2: The default output destinations
Sourcekaim[01-20].ana.nao.ac.jp
kaih[01-12].ana.nao.ac.jp

Targetnwp-sb.ana.nao.ac.jp
nwp-al.ana.nao.ac.jp

Place
Subaru building open-use room
ALMA building room 101

Use the “lpall” command to output data to a network printer. Please refer to Section 6.1.1 for details.

39

Chapter 8

How to use open-use rooms
8.1

About open-use rooms

There are open-use rooms in the South building and Subaru building on the NAOJ Mitaka campus. Theserooms are provided to support user’s researches. Users can analyze astronomy data using computers andmake posters using large-format printers. Every afternoon from Monday to Friday, an operator is in each
open-use room and supports users.
Note that ADC also manages computers and printers in the ALMA building room 101, but the roomis owned by the NAOJ Chile observatory. You need to get permission from the NAOJ Chile observatory
before entering the room. Please ask the NAOJ Chile observatory if you have any question about the room
101.
Table 8.1: List of open-use rooms

Place
Extension number
Opening hours ofoperator desk
Usable machinesSouth building open-use room Subaru
building
A and Broom
2F, South building
1F, Subaru building
3578
3505
At 13:00 - 17:30 from Monday to Friday
Open-use linux terminals (13units), open-use computers (4units), A4 printers (1 unit),
Large-format printers (2 units)

open-use

MDAS terminals(5 units), Openuse PCs (3 units), A4 printer (1unit), Large-format printer (1 unit)• Please refer to Section 4.3 for details on how to use the MDAS terminals.

8.2

How to use open-use linux terminals

Open-use linux terminals are computers constructed for SSH connection to the interactive data analysis
servers and light processing. Note that the terminals have been renamed from the remote login terminal
computers since March 2023.

8.2.1

System conﬁguration

The open-use linux terminals consist of 13 computers located in the South building open-use room A. The
CentOS Release 7 is installed as the Operating System.

40
Table 8.2: Speciﬁcation of the open-use linux terminals
Host nameMachineQuantity
OS
CPU
RAM

8.3

new-r[01-13].adc.nao.ac.jp
HP Z4 G4 Workstation
13
CentOS Release 7Intel Xeon W-2123 3.6 GHz 4 core
16GB

Software conﬁguration of the open-use linux terminals
Table 8.3: List of the software conﬁguration of the open-use
linux terminals

Softwareanaconda3
ds9
emacs
fv
gcc
gnuplot
Google Chromeimagemagick
iraf
jupyter-notebook
pythonastropyipythonmatplotlib
nose
numpy
pyraf
urwid

VersionNotes
2019.03
7.8.0.1
24.3.15.5
4.8.5
4.6 patchlevel 2
Latest Ver.
6.7.8-92.16.1
6.0.0
2.7,3.7
Python modules(except)
3.2.1
7.6.1
3.1.0
1.3.7
1.16.42.1.152.0.1

tcl/tkx11iraf

8.5
2.0beta

8.3.1

How to login

Only guest account “kyoudou” is available to login to the open-use linux terminals. Please click the “kyoudou” account on the display, and input the password “kyoudou”.

8.3.2

Disk areas

The following disk areas are available on the open-use linux terminals.
Table 8.4: Disk areas available on the open-use linux terminals

41
Area
Local disk space

8.3.3

Mount point/home

Size per a mount point
1.9TB

Soft/Hard limit–

Retention period–

Usage notes• SSH connection to the open-use linux terminals is not permitted for a security measure.
• It is prohibited to use more than one computer by one user simultaneously.

8.4

How to use open-use PCs

There are open-use PCs in the South building open-use room B and Subaru building open-use room. Users
can make poster data and output the data to large-format printers using the open-use PCs. Windows orMacintosh is installed in each PC. You do not need to apply for using the open-use PCs.

8.4.1

System conﬁguration

The open-use PCs are intended to be used for the production and printing of posters. Each PC has RAMs
over 32GB to handle large size poster data having many images. Note that the language setting of themnwin2 and mnmac2 is English.
Table 8.5: List of the open-use PCs in the South building
open-use room B
Hostmnwin1
mnwin2
mnmac1
mnmac2

MachineEPSON Endeavor MR8400
EPSON Endeavor MR8100
Apple iMac 2020
Apple iMac 2017

OS
Windows
Windows
macOS
macOS

CPU
Intel Core i5-12600K
Intel Core i7-8700K
Intel Core i5 3.1GHzIntel Core i7 4.2GHz

RAM
32GB
64GB
32GB
64GB

Table 8.6: List of shared PCs in the Subaru building openuse room
Hostsbwin1sbwin2
sbmac1

8.4.2

MachineEPSON Endeavor Pro5700-M
EPSON Endeavor MR7300
Apple iMac Retina

OS
Windows
Windows
OSX El Capitan

CPUIntel Core i7-6700K
Intel Core i7-9700K
Intel Core i7 4.0GHz

RAM
32GB
32GB
32GB

Software conﬁguration of the open-use PCs
Table 8.7: List of the software conﬁguration of the open-use
PCs in the South building open-use room B

mnwin1
SoftwareAdobe Creative Cloud

Notes
Acrobat, Illustrator, Photoshop, Premiere Pro, Media Encoder, Camera Raw

42
Microsoft Oﬃce Homeand Buisiness 2021
FirefoxGnuplot
MobaXterm
PeaZipPowerShell
VNC Viewer
WinSCPEPSON Scan
Yonde!!kokomnwin2
SoftwareAdobe Creative Cloud
Microsoft Oﬃce 2016
CyberLink
PowerDVD 14
ESET Endpoint AntiVirus
FirefoxTera Term
WinSCP
Lhaplusmnmac1
SoftwareAdobe Creative Cloud
Microsoft Oﬃce
iWork
Xcode
mnmac2
SoftwareAdobe Creative Cloud

Microsoft Oﬃce
iWork
GIMP
ParaView
StuﬀIt Expander
XcodeWord, Excel, PowerPoint

Driver for DS-70000

Notes
Acrobat, Illustrator, Photoshop, Premiere Pro
Word, Excel, PowerPoint, Access, Publisher

Notes
Acrobat, Photoshop, Illustrator, Premiere Pro, Media Encoder, Camera Raw
Word, Excel, PowerPoint
Pages, Numbers, Keynote

Notes
Acrobat, Adobe Color, After Eﬀects, Behance, Bridge, Character Animator, Illustrator, InDesign, Lightroom, Media Encoder, Photoshop,
Portfolio, Premiere Pro, Spark
Word, Excel, PowerPoint
Pages, Numbers, Keynote

Table 8.8: List of the software conﬁguration of the open-use
PCs in the Subaru building open-use room
sbwin1
SoftwareAdobe Creative Cloud
Microsoft Oﬃce 2016
CyberLink
PowerDVD 12

Notes
Acrobat, After Eﬀects, Character Animator, Illustrator, InDesign, Media Encoder, Photoshop, Premiere Pro
Word, Excel, PowerPoint

43
Firefox
GIMP
Gnuplot
Google Chrome
IDL 8.1
Nero Express
PuTTY
ScanSnap Manager
Tera Term
WinSCP
Xming+Lhacasbwin2
SoftwareAdobe Creative Cloud
Microsoft Oﬃce 2013
ASTEC-X
CyberLing
PowerDVD 10
Firefox
GIMP
Gnuplot
IDL 8.1
Nero Express
PuTTY
Tera Term Y
WinSCP+Lhacasbmac1
SoftwareAdobe Creative Cloud
Microsoft Oﬃce 2019
iWork
FileZilla
GIMP
Gnuplot
ParaView
StuﬀIt Expander
Xcode

8.4.3

Notes
Acrobat, After Eﬀects, Bridge, Character Animator, Illustrator, Media
Encoder, Photoshop, Premiere Pro
Word, Excel, PowerPoint

Notes
Acrobat, After Eﬀects, Character Animator, Illustrator, InDesign, Media Encoder,Photoshop, Premiere Pro
Word, Excel, PowerPoint
Pages, Numbers, Keynote

How to use open-use PCs

The open-use PCs are always logged-in by user “kyoudou”. If logged-out, please log-in with the following
account and password.

Account: kyoudou
Password: kyoudou
Note that you should delete your ﬁles on the open-use PC after use because the these PCs are used byunspeciﬁed users. If user’s ﬁles remain, operators delete the ﬁles once a month.

44

8.5

How to use printers and scanners

There are A4 network printers, large-format printers, and scanners in the South building open-use room B,
and the Subaru building open-use room. Users can input/output documents using these devices. You do
not need to apply for using these devices.

8.5.1

System conﬁguration
Table 8.9: List of printersSouth building open-use room B
Host
IP address
nwp-m1.ana.nao.ac.jp 133.40.130.137
lfp-m2—
lfp-m3—
Subaru building open-use room
Host
IP address
nwp-sb.ana.nao.ac.jp
133.40.130.139
lfp-sb—FormatA3
Large-format
Large-format

Printer
Fujiﬁlm ApeosPrint C5240
EPSON SC-P1005PS
EPSON SC-P1005PS

FormatA4
Large-format

Printer
Fujiﬁlm ApeosPrint C5240
EPSON SC-P1005PS• Large-format printers are available only from the open-use PCs.
• The lfp-m3 is a dedicated printer to use cloth paper.

8.5.2

How to use the network printers

There are A4 network printers in the South building open-use room B and Subaru building open-use room.
A4 papers are loaded in the network printers. Users can output data from the open-use PCs or user’s PC
on the NAOJ network. Please refer to an instruction manual of each application for printing procedure. To
use the network printer from the user’s PC, the network printer driver must be installed.
How to install a network printer driver
Following URL is a link to the network printer driver. Please install the driver according to the instructions
on the link.
• Driver: https://www.fujifilm.com/fb/download/eng/aprt/c5240
About printer supplies
Printer supplies such as papers and toners are prepared near the network printer. Operators exchange
supplies with new ones, but in the case that operators are absence, you have to exchange the supplies
yourself. After exchanging supplies, please ﬁll in a form in the record book near the network printer.

8.5.3

How to use large-format printers

There are large-format printers in the South building open-use room B and Subaru building open-use room.
Super A0 or super B0 roll papers with glossy or plain are available. The “lfp-m3” located in the Southbuilding open-use room B is a dedicated printer to use cloth papers, so super A0 or super B0 cloth roll
paper. Users can output data only from the open-use PCs (output from the user’s PC is prohibited). Afterusing the large-format printer, please ﬁll in a form in the record book near the printers.
The following description is how to use the large-format printer from Windows and Macintosh open-use
PCs. Usually, a super A0 glossy roll paper is loaded in the “lfp-m2”, and “lfp-sb”, and super A0 cloth roll
paper is loaded in the “lfp-m3”, respectively. If you want to use other papers, operators exchange the paper,but in the case that operators are absence, you have to exchange the paper yourself.

45
From Windows
The following description is the way to output data from the Adobe Acrobat on the Windows open-use
PC(mnwin2) to a large-format printer.
1. Click the “File” tab and click the “Print”.
2. In the “Printer” select box, select a printer name. The choice is depending on whether the print size isdeﬁned size (e.g. A and B series paper sizes) or not (e.g. long-size printing). Note that the “lfp-m3”
and “lfp-m3 PostScript” are the dedicated printer to use cloth papers.
• Deﬁned paper size: lfp-m2, lfp-m3, lfp-sb• Undeﬁned paper size: lfp-m2 PostScript, lfp-m3 PostScript, lfp-sb PostScript
3. Click the “Properties”.
4. In the “Media Type” select box of the “Main” tab, select a type as follows:• When a glossy role paper is loaded: EPSON Pro Photo <Glossy>• When a plain role paper is loaded: EPSON Plain Paper <Singleweight>• When a cloth role paper is loaded: EPSON MC/PM Cloth
5. In the “Source” select box, select a “Roll paper”.
6. In the “Size” select box, select a print size you want .
7. In the “Output Paper” select box of “Paper Layout” tab, select a paper size loaded (super A0 or super
B0).
8. Set the “Scale” to 100% or any scale.
9. Click the “OK”.
10. Click the “Print”.
The “lfp-XX PostScript” in the “Printer” select box can perform long-size printing but cannot display aprint preview window. Depending on the application used, the print dialog box may vary, so if you haveany questions, please contact operators.
About printer supplies
Printer supplies such as papers and toners are prepared near the large-format printers. Operators exchange
supplies with new ones, but in the case that operators are absence, you have to exchange the supplies. Afterexchanging supplies, please ﬁll in a form in the record book near the large-format printers.

8.5.4

How to use scanners

There are scanners in the South building open-use room B and Subaru building open-use room. Eachscanner can be available from the open-use PCs.
Table 8.10: List of scanners
Place
South building open-use room B
Subaru open-use room

MachineEPSON DS-70000
Fujitsu ScanSnap iX500

Max. available paper
A3
A4

Connected PC
mnwin1sbwin1Each scanner is connected to a open-use PC with Japanese setting. If you want to use scanners, pleasecontact an operator.

8.6

Network connection

The NAOJ network and the Internet are available in the NAOJ Mitaka campus. Accesses from the NAOJ
network to the Internet is permitted, but in contrast, from the Internet to the NAOJ network is not
permitted for a security measure. This section introduces a usage of the NAOJ network and the Internetin the open-use rooms.

46

8.6.1

NAOJ network

In the open-use rooms, Wi-Fi of the NAOJ network is available, but only the NAOJ staﬀs can use it. Pleaserefer to a website of the NAOJ NETWORK SERVICE HELP CENTER (https://nethelp.mtk.nao.ac.
jp/contents/) for usage of the NAOJ network(this web site is not accessible from the Internet).

8.6.2

Internet

The Internet can be used in the NAOJ Mitaka campus. Wired LAN is available in the open-use rooms, and
Wi-Fi is available throughout the NAOJ Mitaka campus. In order to access the interactive data analysis
servers or to use network printers, VPN connection to the NAOJ network must be established in advance.
Wired LAN
There are network hubs for connecting the Internet in the South building open-use room A,B and Subaru
building open-use room. IP addresses are allocated by DHCP.
Wireless LAN
Wi-Fi is available throughout the NAOJ Mitaka campus. The SSID of the Wi-Fi is “naoj-open”. Pleaseask NAOJ staﬀs for the password or see the digital information signage in each building. The password is
updated once a week.

47

Update history
2023-10-17

2023-10-11
2023-09-25
2023-08-16
2023-07-20
2023-05-26
2023-05-19

2023-03-24

2023-02-09
2023-02-07
2022-12-23
2022-11-02
2022-06-07
2022-05-23

2022-04-04
2022-02-02
2021-12-23
2021-10-13
2021-09-09
2021-08-19
2021-08-04
2021-06-18
2021-06-11
2021-04-19

2020-12-24
2020-11-27
2020-10-16
2020-08-26
2020-08-03

Added“CASA6.5.4(pipeline)”
into
Section
5.1.
Added“CASA6.4.1(pipeline)(casa-6.4.1-12-pipeline-2022.2.0.68)”
and“CASA6.5.4(pipeline)” into Section 5.3.
Added “CASA6.6.0” into Section 5.1.
Added “CARTA4.0” into Section 5.1.
Modiﬁed CARTA’s instruction in Section 5.2.15.
Added “CASA6.5.6” into Section 5.1.
Added “CARTA3.0”, “CARTA4.0beta”, “HEALPix Facility”, Pgperl into Section 5.1. Added Section 5.2.15. Added compact PC into Section 4.3.1.
Revised documents.
Removed Section 5.2.
Added “CASA6.5.5” and“IRAF2.17”, and replaced “Intel Parallel Studio XE Composer Edition” to“Intel oneAPI” in Section 5.1.
Revisedsections
becausetheloadbalancer(kaim.ana.nao.ac.jp,
kaih.ana.nao.ac.jp), large format printer(lfp-m1, lfp-al), A3 printer(nwp*),
and terminal workstations(sbt*, alt*) are no longer in operation.
Corrected the full path of CASA6.4.1 in Section 5.3.
Added “CASA6.5.3” into Section 5.1.
Added “NFS areas for data migration” into Section 4.1.3. Removed “nfsdf”
command from Section 6 because it is not implemented.
Added “CASA6.5.1”, “CASA6.5.2” and “CASA6.4.1” into Section 5.1.
Added “CASA6.5.0” and “getsf” into Section 5.1.
Added “CASA 6.4.4” into Section 5.1. Upgraded “IDL” from 8.8 to 8.8.1,“Intel Parallel Studio XE Composer Edition” from 2020 update4 to 2022.1.2,“Mathematica” from 12.2.0 to 13.0.1, and “PBS” from 2021.1.0 to 2021.1.2.
Added “DisPerSE” and “devtoolset-11” into Section 5.1.
Added “CASA 6.4.3” into Section 5.1.
Added “CASA 6.4.0” into Section 5.1.
Added “CASA 6.2.1” into Section 5.1.
Added “CASA 6.3.0” into Section 5.1.
Revised “How to start IRAF 2.14” in Section 5.3.
Revised Section 4.2.5, 6.1.2 and 6.1.3.
Added “CARTA 2.0” into Section 5.1. Revised Section 5.3.2.
Added “CASA 5.8.0” and “6.2.0” into Section 5.1.
Added “CASA 6.1.1” into Section 5.1. Upgraded “IDL” from 8.7.3 to 8.8, “Intel
Parallel Studio XE Composer Edition” from 2020 Update 1 to 2020 Update 4,“Mathematica” from 12.0.0 to 12.2.2 in Section 5.1.
Added “CASA 5.7.0”, “CASA 5.7.2”, “CASA 6.1.0”, “CASA 6.1.2”, and“CARTA 1.4” into Section 5.1.
Revised Section 4.2.4.7.
Revised Section 4.2.4.7. Modiﬁed “xmacs” to “xemacs” and gcc to GCC in
Section 5.1.
Revised Section 4.2.
Added “CARTA 1.3” into Section 5.1.

48
2020-07-20

2020-05-28
2020-05-11
2020-04-20
2020-03-11
2020-02-14
2020-02-13
2020-01-28
2020-01-22
2019-12-24
2019-12-23
2019-12-03
2019-11-26
2019-10-23
2019-10-21
2019-10-18
2019-08-23
2019-07-19
2019-07-16
2019-07-04
2019-07-02

2019-04-18
2019-04-15

2019-02-21

2018-11-19
2018-10-31
2018-09-05
2018-08-20
2018-07-31
2018-07-04

Revised Section 4.2. Added “AIPS(31DEC19)”, Python3.8, and modules of
Python3.8 (APLpy 2.0.3, astropy 4.0.1.post1, dustmaps 1.0.4, healpy 1.13.0,
ipython 7.16.1, jupyter 1.0.0, matplotlib 3.2.2, notebook 6.0.3, numPy 1.18.5,
pandas 1.0.5, Pmw 2.0.1, pymultinest 2.9, pyqtgraph 0.11.0, PyQt5 5.15.0,
pyraf 2.1.15, pyregion 2.0, pyspeckit 0.1.23, requests 2.24.0, rpy2 3.3.5, scipy
1.5.1, seaborn 0.10.1, stsci.tools 3.6.0, urwid 2.1.0) into Section 5.1. Upgraded“CFITSIO” from 3.42 to 3.48, “Gnuplot” from 5.2.2 to 5.2.8, ds9 from 8.0.1
to 8.1, IDL Astronomy User’s Library from 21-Nov-2017 to 27-Feb-2020, WCSTools from 3.9.4 to 3.9.6 in Section 5.1. Revised Section 5.3 (AIPS).
Added “Google Chrome” into Section 5.1.
Revised Section 5.3 (AIPS).
Removed “Google Chrome” from Section 5.1.
Added “PyQt5” and “pyqtgraph” into Section 5.1.
Updated software conﬁguration of sbmac1 in Section 8.2.2.
Removed “PyFITS” From Section 5.1 because “PyFITS” is included in “Astropy”.
Added description of Karma into Section 5.3.
Removed “Pgperl” From Section 5.1 because “Pgperl” does not exist in thissystem. Updated Section 4.1.3 and 4.3.3.
Added “CASA 5.6.2” and “CARTA 1.2.1” into Section 5.1.
Updated “List of shared PCs in the South building open-use room B” in Section
8.2.1.
Added “CASA 5.6.1” into Section 5.1.
Added “Karma” into Section 5.1.
Updated difmap from 2.5a to 2.5e in Section 5.1.
Updated Section 5.2.
Updated Section 5.2.
Corrected full path of CASA in Section 5.3.
Added descriptions of qhold and qrls commands into Section 4.2.4. Added
Section 4.2.5.
Added “CASA 5.5.0” and “CARTA” into Section 5.1.
Proofreading this document.
Corrected the information of the NAOJ VPN service in Section 3.2, revised
Section 4.1.3 and 4.3.3 because of change policy of the periodic deletion, revised
Section 4.4.1, 4.4.2, 4.4.3 and 5.2 because of a replace of the remote login
terminal computers.
Updated the information of mnmac2 in Section 8.2.
Added Chapter 8. In Section 5.1, added “CASA 5.4.1”, updated IDL from
8.6.1 to 8.7.2, updated PBS from 14.2.4 to 18.2.3, updated Intel Parallel StudioComposer Edition from 2018 update 1 to 2019 update 3, updated Mathematica
from 11.2.0 to 11.3.0, and updated ds9 from 7.5 to 8.0.1. Added a full-pathof CASA 5.4.0 into the description of CASA in Section 5.3. Updated theinformation of mnwin2 in Section 8.2.
Added “PySpecKit” into Section 5.1. We added precautions for use of Jupyter
Notebook. Added a full-path of CASA 5.4.0 into the description of CASA in
Section 5.3.
Corrected URLs of links.
Added “CASA 5.4.0” into Section 5.1. Added a full-path of CASA 5.3.0 into
the description of CASA in Section 5.3.
Added “pandoc” and “seaborn” into Section 5.1.
Added “difmap” into Section 5.1.
Revised Section 4.3.2. Added “2. How to write to BD medias using the CUI
commands” and “3. How to use tape device” into Section 7.2.2.
Added CASA 5.3.0 into Section 5.1. Added a full-path of CASA 5.1.2 into
the description of CASA in Section 5.3. Added description of MCSRED into
Section 5.3. Removed description of CFITSIO in Section 5.3. Added Section
7.2.2.

49
2018-06-25
2018-06-08
2018-05-25

2018-05-18
2018-04-27

2018-04-25

2018-04-13

2018-03-12
2018-03-05
2018-03-02
2018-02-26

2018-02-16

2018-02-15

Revised Section 7.2.1 and Section 5.3 (AIPS, GILDAS, and Miriad).
Added Section 7.2.
Added sentences into “How to use remote login terminal computers”. Added
PDL and cpanm into “Software conﬁguration of the interactive/batch processing data analysis servers and terminal workstations”.
Revised the structure of the chapters.
Added “How to use interactive data analysis servers”. Added “How to use
network printers”. Added CosmoloPy, dustmaps, GCC 3.4.6, Healpy, Montage, pyregion, urwid, Requests, and Jupyter Notebook into “Software in theinteractive/batch processing data analysis servers and terminal workstations”.
Added CASA Analysis Utilities into “Software conﬁguration of the interactive/batch processing data analysis servers and terminal workstations”. Added“how to use the CASA Analysis Utilities” into “How to use software”.
Added CASA 5.1.2 and lz4 into “Software conﬁguration of the interactive/batchprocessing data analysis servers and terminal workstations”. Revised “How to
use batch processing data analysis servers”.
We added “nfsdf” into “Unique commands of the MDAS”. Added “Peripherals”
and “How to use batch processing data analysis servers”.
Revised sentences in “How to access the Multi-wavelength Data Analysis System”.
Speciﬁed that CosmoloPy, Healpy, pyregion, urwid, Requests, APLpy, and lz4
have not yet been installed.
Revised sentences in “Application of the Group ID service”. Added CosmoloPy,
Healpy, pyregion, urwid, Requests, APLpy, and lz4 into “Software in the interactive/batch processing data analysis servers and terminal workstations”.
Added “How to use software”.
Removed an incorrect explanation in “Access from the client terminal on the
NAOJ network”. Added an explanation about the MDAS VPN service into
“How to use the MDAS VPN service”.
First edition was issued.