How to submit your proposal via the webform
Applicants are requested to access the ProMS2.0 page to fill the webform for the application form and upload necessary files (e.g., PDF files of Scientific Justification). Please refer to 'ProMS2_guide.pdf' for the instruction.
We recommend that you read Call for Proposals carefully. Any questions related to proposal submission should be forwarded to 
.
Normal/Intensive Application Form
The subsections with (*) will be hidden from reviewers. For other subsections, please follows the Dual Anonymous (DA) writing style described in Section 3.
For PFS applicants, please use the PFS forms described below.
1. Title of Proposal
Provide a short title for your proposal.
2. Principal Investigator (*)
Provide contact details for the PI.
The information provided in the 'Gender' and 'PhD Year' sections is utilized exclusively for statistical analysis aimed at identifying potential biases. This data will not appear in the proposal, and reviewers will not have access to them.
3. Scientific Category
Please select appropriate one out of following 23 categories:
(1) Solar System (2) Evolved Extrasolar Planets (3) Young Extrasolar Planets (4) Planet Formation (5) Star Formation
(6) ISM (7) Stars and Brown Dwarfs (8) Stellar Envelope and Activity (9) Compact Objects and SNe (10) Milky Way
(11) Galactic Archaeology (12) Local Group (13) Nearby Galaxies (14) IGM and Abs. Line Systems (15) Circumgalactic Medium
(16) Cosmology (17) Gravitational Lenses (18) Clusters and Proto-Clusters (19) Environmental Effect on Galaxies
(20) High-z Galaxies (LAEs, LBGs) (21) High-z Galaxies (others) (22) AGN and QSO Activity (23) Miscellaneous
This is used to combine similar proposals into the same category group. Please note, however, that the category specified by an applicant may be changed in the reviewing process according to its contents. Each Normal/Intensive program proposal will be reviewed usually by 5 referees (anonymous) who are experts in the relevant category.
4. Abstract (except for Service Program)
Provide a clear and concise description of your proposed observations and their scientific importance in approximately 200 words. The abstract of all the accepted Subaru proposals will be open to the public after the time of the data release (i.e., when the proprietary period of 18 months has expired).
5. Co-Investigators (*)
List the first and last names and affiliations, and email addresses of co-investigators. Please obtain consents of all co-investigators for his/her being included in this list, since e-mail notification will be sent to them just after the deadline of application. All potential observers should be listed here. Please avoid using the name of a team or group. You can append the "CoI" field as many as you like (In case that the number of these co-investigators is large, the names of some members may not appear on the formatted cover page, however, our database certainly stores all the records of co-investigators listed on the webform). Please answer the question of 'How many students do you have among CoI?'. This is just for educational statistics and will not be used for the screening.
6. Thesis Work (*)
If the observations will form part of a graduate student's thesis project, please provide the student's name and thesis title.
7. Intensive Programs
If you are submitting an Intensive Program proposal, please select 'yes'. Intensive proposals using Keck instruments are not allowed. Those using Gemini instruments can be submitted only for B semesters (March deadline).
8. List of Applicant's Related Publications (*)
List publications (with full citation) related to the proposal.
9. Condition of Closely-Related Past and Scheduled Observations (*)
If your proposal is a continuation of (or inextricably related with) the previously accepted proposals, describe how the relevant past observations were carried out by giving the Open Use proposal ID, Title, Weather/Observational condition, Achievement rate [in %] for the planned outcome.
Additional remarks:
(a) The proposals described here must be included also in the following "1-10 Post-Observational Status and Publications".
(b) The reason why you request observational time in this semester (in spite of the past experience of Subaru observations on a similar/the same theme) has to be briefly described at the end of the "Scientific Justification" (e.g., bad weather/condition, telescope/instrument down time, expansion/improvement of the data, observing targets in different season).
10. Post-Observation Status and Publications (*)
Report the status or outcome of your main Subaru Observations carried out in the past. All observations relevant to this proposal (e.g., those enumerated in 1-9) must be included here. Similarly, all observations in the past 3 years with which the applicant was involved as PI must be reported. Give the date, the Open Use proposal ID (e.g., S01B-999), PI's name, status of data reduction/analysis, and related publications. For HSC queue mode programs with Grade A or B, specify (Grade, completion rate) [for example, (A,90%)] in the 4th status column. Queue programs of Grade C or Filler programs do not need to be reported unless they have been executed.
11. Team Expertise (*)
Please describe your team expertise to conduct the proposed science program.
12. Observing Run
List the instruments, the requested and minimum acceptable number of nights, preferred and acceptable dates (e.g., "Apr/01-May/31"), lunar phase (Bright, Gray or Dark), and Observing Modes.
Dark time is defined as being within 3 nights of the New Moon, Bright time is within 3 nights of the Full Moon, and Gray time is the remaining part of the lunar cycle.
Applicants who request Dark time for infrared observations should justify its necessity in their scientific justification.
If you propose AO observations, please select the correct combination in the instrument list among NGS-AO188, LGS-AO188, and NIRWFS-AO3k.
Possible 2nd choice Instruments: If your science goal can (fully or partly) be achieved by the instruments (of Subaru/Keck/Gemini) other than your 1st choice instrument, you could describe such alternative instruments as 2nd choice instruments.
13. Scheduling Requirements
Any other special scheduling requirements should be clearly explained here, especially when you request bright/gray nights while there are still unacceptable dates affected by the Moon.
14. List of Targets
List all the targets intended for observations. Please use equinox J2000.0 unless otherwise specified in comments. If you have comments on targets, please indicate them in the field for comments.
Notes for PFS: Use the PFS Target Uploader to submit the target list and then paste the Upload ID in the boxes at the bottom of this section. Please refer to the PFS Target Uploader User Guide for detailed instructions. The Upload ID is not mandatory in the PFS Classical form if the targets are not available at the time of the proposal submission (e.g., transient, ToO targets). Please describe a summary of areal coverage, number of targets, and source density in the comment box, which is mandatory for technical reviews.
15. Observing Method and Technical Details
Describe your proposed observations. Please explicitly state the instrument configuration (filters, slit width, readout mode) and justify the requested time by describing the details of your proposed observations, with reference to the instrument sensitivities provided on the website. Please justify the minimum nights requirements. Please give sufficient information so that the feasibility of proposed observations can be confirmed, and so that support astronomers can prepare for observations.
If you propose AO observations, please describe the nature of the targets (extended or point source) as well as the guide star properties (see the Planning Observations with Subaru AO188, and with NIRWFS for details).
If you propose PFS Classical observations, please follow the template for Classical mode provided on the PFS website to fill out this section.
16. Instrument Requirements
HSC applicants must explicitly describe the filters they intend to use, where the desired set as well as the minimum acceptable set should be clearly specified here. Other specific or unusual instrument requirements should be explained here.
17. Backup Proposal in Poor Conditions
Provide a short description of observations which will be carried out if conditions are not good enough for the main purpose (e.g., poor transparency). Please specify target names.
18. Public Subaru Telescope Data Archive
Check your targets in SMOKA database (Public Data Archive) before your submission. If your targets have already been observed by Subaru in the past, please describe why you need to observe them again.
19. Justify Duplications with the on-going SSP
For PFS applicants who request to observe the same fields or targets as observed with PFS SSP, please describe the differences between your program and the SSP.
Service Program Form
For Service Programs, 'Requirements of Observation' should be written in the plain text according to the specific instructions detailed on the service program webpage. Then, upload the plain text file via the webform.
PFS Queue/Community Filler Forms
This section describes items specific to the PFS forms. For other items, please refer to Normal/Intensive Application Form described above.
PFS Queue
12. Pointing Simulation
To fill out this section, please run pointing simulations using the PFS Target Uploader. Please refer to the PFS Target Uploader User Guide and the PFS website for detailed instruction.
14. Target List ID (Upload ID)
Use the PFS Target Uploader to submit the target list after the pointing simulations. Copy the Upload ID and paste it into a box in this section. Also, please describe a summary of areal coverage, number of targets, and source density in the comment box, which is mandatory for technical reviews.
15. Observing Method and Technical Details
Please follow the template for Queue mode provided on the PFS website.
17. Justify Duplications with the on-going SSP
Please describe the differences between your program and the PFS-SSP following the policies described on the PFS website.
[Closed for S25B] PFS Community Filler
7. Target List ID (Upload ID)
Use the PFS Target Uploader to submit the target list. Copy the Upload ID and paste it into a box in this section. Also, please describe a summary of areal coverage, number of targets, and source density in the comment box, which is mandatory for technical reviews.
8. Justify the program as a filler and duplications with the on-going SSP
Please describe (1) why a normal program does not fit to carry out the proposed observation, and (2) the differences between your program and the PFS-SSP following the policies described on the PFS website.
How to Prepare the Scientific Justification
*** Applicants should read the Dual Anonymous Guidelines (Japanese/English) before writing the Scientific Justification. ***
The PDF file of the Scientific Justification may in principle be freely prepared without any specific format; however, the following conditions should be fulfilled. Proposals violating any of these requirements may be disqualified without being reviewed.
| language: | Should be written in English. |
|---|---|
| header information: | At the top of the first page, the title of the proposal should be clearly written (see also [note] on service program). |
| font size: | Use font no smaller than 10 points (even in the figure caption or in the reference). |
| figures: | Color figures can be included. However, proposals will be sent to referees electronically, and reproducibility of color figures may depend on the referees' environments. |
| margins: | Keep sufficiently large margins (at least 15 mm) at each of the four sides, so that any missing could be avoided when printed out. |
| page limitation: | including figures, tables and references. (for A4 or letter size paper)
|
| file size: | The file size should not exceed 4MB. |
| file name: | The name of the file should end with ".pdf". |
| the DA writing style: |
|
For more details please follow the Dual Anonymous Guidelines (Japanese / English).
More practical examples can be found in the DA Guidelines of ALMA.
[1] For Service Program applicants, a brief abstract (e.g., a few lines) should be presented after the title of the proposal.
updated on February 4, 2025