From f8249138623aeb67911ce7dea863ea4839de3082 Mon Sep 17 00:00:00 2001
From: "Grzegorz (Greg) Madejski" <36776103+Madejski@users.noreply.github.com>
Date: Tue, 17 Dec 2024 15:31:27 -0800
Subject: [PATCH] Update portal-intro.rst

---
 data-access-analysis-tools/portal-intro.rst | 9 +++++----
 1 file changed, 5 insertions(+), 4 deletions(-)

diff --git a/data-access-analysis-tools/portal-intro.rst b/data-access-analysis-tools/portal-intro.rst
index 7e4d2d78..35d12061 100644
--- a/data-access-analysis-tools/portal-intro.rst
+++ b/data-access-analysis-tools/portal-intro.rst
@@ -28,15 +28,16 @@ That table contains "forced" flux measurements in locations of all objects which
 The table ``dp02_dc2_catalogs.DiaObject``, in turn, contains objects which were detected using the "Difference Image Analysis" (DIA) method.
 The DIA method basically subtracts the fluxes of the previously undetected objects from those that showed ``SNR > 5`` detections in individual single-epoch difference images.
 
-This example demonstrates how to create a forced photometry lightcurve for the known RR Lyrae star located at (62.1479031, -35.799138).
+This example demonstrates how to create a forced photometry lightcurve for the known RR Lyrae star located at (62.1479031, -35.799138) using the Portal aspect of the Rubin Science Platform.
 
 The individual Processed Visit Images might have very slightly different coordinates for the same object.
 With this, instead of providing the RA and Dec to the light curve extraction process, it is wise to extract the data from the ``dp02_dc2_catalogs.DiaObject`` table using the object's unique DIA object identifier ``diaObjectId``.  
 Determining the ``diaObjectId``  can be accomplished via the Portal Aspect of the Rubin Science Platform, by clicking on the "UI assisted" button, selecting "DP0.2 Catalogs" tab, chosing the "dp02_dc2_catalogs" on the left, and "dp02_dc2_catalogs.DiaObject" table on the right.
 
-Only the spatial constraints need to be entered on the left, with the 62.1479031, -35.799138 - and a 2 arcseconds radius using the "cone Shape" ("Temporal" constraints button needs to be unchecked).
-For the "Output Column Selection" only the ``diaObjectId`` and needs to be checked.  
-Pressing the "search" button will return only one ``diaObjectId`` - it is 1651589610221864014.
+Only the spatial constraints need to be entered on the left, with the 62.1479038, -35.7991348 - and a 2 arcseconds radius using the "cone Shape" ("Temporal" constraints button needs to be unchecked).
+For the "Output Column Selection" only the ``diaObjectId`` and ``gPSFluxNdata`` need to be checked.
+(The ``gPSFluxNdata`` will return the number of observations in the ``g`` band, and if there are multiple objects in the search radius - the one with a larger mumber of data points needs to be selected.)
+Pressing the "search" button will return two ``diaObjectId``.  The one with a larger number of data points is 1651589610221862935.  
 
 The ``ForcedSourceOnDiaObject`` contains fluxes of individual objects, but it does not contain the observation epochs;  however, the table ``CcdVisit`` does.
 Obtaining the visit epochs will require joining two tables - specifically ``ForcedSourceOnDiaObject`` and ``CcdVisit`` on the common meta entry of ``ccdVisitId``.