DMR++ - Revision history

Ndp at 21:48, 14 November 2024

2024-11-14T21:48:23Z

← Older revision		Revision as of 21:48, 14 November 2024
Line 1:		Line 1:
	'''~~Warning~~'''
	The content of this wiki page has been ~~migrate~~ to ~~a new location on Github~~: https://opendap.github.io/DMRpp-wiki/~~. The content of this document has stopped being updated.~~		<font size="5">
			<font color="red">'''Attention:'''</font> This page is deprecated.

			[https://opendap.github.io/DMRpp-wiki/ The content of this wiki page has been moved to GitHub: https://opendap.github.io/DMRpp-wiki/]
			</font>
			<s>

	''How to build & deploy dmr++ files for Hyrax''		''How to build & deploy dmr++ files for Hyrax''
Line 550:		Line 555:
	** From the '''File''' menu select '''Open Remote Dataset...'''		** From the '''File''' menu select '''Open Remote Dataset...'''
	** Paste the <tt>{gf_url}.html</tt> into the resulting dialog box.		** Paste the <tt>{gf_url}.html</tt> into the resulting dialog box.
			</s>

Mju at 23:59, 19 September 2024

2024-09-19T23:59:25Z

← Older revision		Revision as of 23:59, 19 September 2024
Line 1:		Line 1:
			'''Warning'''
			The content of this wiki page has been migrate to a new location on Github: https://opendap.github.io/DMRpp-wiki/. The content of this document has stopped being updated.

	''How to build & deploy dmr++ files for Hyrax''		''How to build & deploy dmr++ files for Hyrax''

Mju: /* DAP2 UI Test */

2024-09-19T21:25:53Z

DAP2 UI Test

← Older revision		Revision as of 21:25, 19 September 2024
Line 547:		Line 547:
	** From the '''File''' menu select '''Open Remote Dataset...'''		** From the '''File''' menu select '''Open Remote Dataset...'''
	** Paste the <tt>{gf_url}.html</tt> into the resulting dialog box.		** Paste the <tt>{gf_url}.html</tt> into the resulting dialog box.
	~~---~~

Jimg: /* Building dmr++ files with get_dmrpp */

2024-08-29T18:12:27Z

Building dmr++ files with get_dmrpp

← Older revision		Revision as of 18:12, 29 August 2024
Line 246:		Line 246:
	-rw-r--r-- 1 jimg staff 3378674 Aug 28 17:37 AMSR_E_L3_SeaIce25km_V15_20020601.hdf.dmrpp		-rw-r--r-- 1 jimg staff 3378674 Aug 28 17:37 AMSR_E_L3_SeaIce25km_V15_20020601.hdf.dmrpp

	==Building ''~~dmr~~++'' files with get_dmrpp==		==Building ''DMR++'' files for HDF5/NetCDF4 with get_dmrpp==

	The application that builds the ''dmr++'' files is a command line tool called ''get_dmrpp''. It in turn utilizes other executables such as ''build_dmrpp'', ''reduce_mdf'', ''merge_dmrpp'' (which rely in turn on the ''hdf5_handler'' and the ''hdf5'' library), along with a number of UNIX shell commands.		The application that builds the ''dmr++'' files is a command line tool called ''get_dmrpp''. It in turn utilizes other executables such as ''build_dmrpp'', ''reduce_mdf'', ''merge_dmrpp'' (which rely in turn on the ''hdf5_handler'' and the ''hdf5'' library), along with a number of UNIX shell commands.

Jimg: /* Supported Data Formats */

2024-08-29T18:11:48Z

Supported Data Formats

← Older revision		Revision as of 18:11, 29 August 2024
Line 24:		Line 24:
	==Supported Data Formats==		==Supported Data Formats==

	The ''dmr++'' software currently works with ''hdf5'' ~~and~~ ''netcdf-4'' files. (The ''netcdf-4'' format is a subset of ''hdf5'' so ''hdf5'' tools are utilized for both.) Other formats like ''zarr~~'', ''hdf4~~'', ''netcdf-3'' are not currently supported by the ''dmr++'' software, but support could be added if requested.		The ''dmr++'' software currently works with ''hdf5'', ''netcdf-4'', and (experimental as of 8/29/24) ''HDF4''/''HDF4-EOS2'' files. (The ''netcdf-4'' format is a subset of ''hdf5'' so ''hdf5'' tools are utilized for both.) Other formats like ''zarr'', ''netcdf-3'' are not currently supported by the ''dmr++'' software, but support could be added if requested. However, an external group working on the Python Kerchunk software has developed ''VirtualiZarr'' which can parse either Kerchunk or DMR++ documents and read from data those describe using the Zarr API.

	===''hdf5''===		===''hdf5''===
Line 85:		Line 85:

	[http://www.bic.mni.mcgill.ca/users/sean/Docs/netcdf/guide.txn_79.html You can learn more in the NetCDF documentation here.]		[http://www.bic.mni.mcgill.ca/users/sean/Docs/netcdf/guide.txn_79.html You can learn more in the NetCDF documentation here.]

			===''HDF4''/''HDF4-EOS2''===

			This is a complicated case, and its support as of 8/29/24 is still considered experimental. The HDF4 data model is quite complex, more so than the HDF5 model, and we focusing on complete support for those features used by NASA. To this end, we are also working on support for HDF4-EOS2, data files that can only be read correctly with the HDF4-EOS2 library. The main distinction of that API is the treatment of values for the Domain variables for Latitude and Longitude. Our support handles the HDF4-EOS Grid data type and using DMR++ the Latitude and Longitude values appear as users expect, although some aspects of this are ongoing. We do not yet support the HDF4-EOS2 Swath data type.

			Se the section below for information on the tool for building DMR++ files for HDF4 and HDF4-EOS2 data files.

	==Building ''DMR++'' files for HDF4 and HDF4-EOS2 (experimental)==		==Building ''DMR++'' files for HDF4 and HDF4-EOS2 (experimental)==

Jimg: /* Simple shell command */

2024-08-29T00:25:00Z

Simple shell command

← Older revision		Revision as of 00:25, 29 August 2024
Line 215:		Line 215:
	The command, written for the Bourne Shell, is:		The command, written for the Bourne Shell, is:

	<nowiki>#!/bin/~~bash~~		<nowiki>#!/bin/sh
	#		#
	# usage get_dmrpp_h4.sh <file>		# usage get_dmrpp_h4.sh <file>

Jimg: /* Building DMR++ files for HDF4 and HDF4-EOS2 (experimental) */

2024-08-29T00:20:56Z

Building DMR++ files for HDF4 and HDF4-EOS2 (experimental)

← Older revision		Revision as of 00:20, 29 August 2024
Line 182:		Line 182:

	Building the DMR++ and embedding a ''file://'' URL will enable testing the DMR+.		Building the DMR++ and embedding a ''file://'' URL will enable testing the DMR+.
			====Using the server to examine data returned by the DMR++====

	Lets look at how the ''hyrax'' service will treat that data file using the DMR++. In a browser, goto		Lets look at how the ''hyrax'' service will treat that data file using the DMR++. In a browser, goto
Line 187:		Line 188:
	http://localhost:8080/opendap/		http://localhost:8080/opendap/

	~~You will see~~ [[File:Hyrax-including-new-DNRpp.png\|200px\|thumb\|right\|text-~~bottom~~\|The running server shows the DMR++ as a dataset.]]		[[File:Hyrax-including-new-DNRpp.png\|200px\|thumb\|right\|text-top\|The running server shows the DMR++ as a dataset.]]

	Click on the your equivalent of the '''3B42.20130111.09.7.HDF'' link, subset, download and open in Panoply or the equivalent. [[File:Hyrax-subsetting.png\|200px\|thumb\|right\|text-~~bottom~~\|Use the form interface to subset and get a response.]]		Note: ''The server caches data catalog information for 5 minutes (configurable) so new items (e..g., DMR++ documents) may not show up right away. To force the display of a DMR++ that you just created, click on the source data file name and edit the URL so that the suffix '''.dmr.html''' is replaced by '''.dmrpp/dmr'''.''

			Click on the your equivalent of the '''3B42.20130111.09.7.HDF'' link, subset, download and open in Panoply or the equivalent. [[File:Hyrax-subsetting.png\|200px\|thumb\|right\|text-top\|Use the form interface to subset and get a response.]]

	You can run batch tests in lots of files by building many DMR++ documents and then asking the server for various responses (nc4, dap) from the DMR++ and the original file. Those could be compared using various schemes, although in its entirety that is beyond this section's scope, the command ''getdap4'' is also included in the container and could be used to compare ''dap'' responses from the data file and the DMR++ document.		You can run batch tests in lots of files by building many DMR++ documents and then asking the server for various responses (nc4, dap) from the DMR++ and the original file. Those could be compared using various schemes, although in its entirety that is beyond this section's scope, the command ''getdap4'' is also included in the container and could be used to compare ''dap'' responses from the data file and the DMR++ document.

	~~Here~~ is a comparison of the same underlying data, the left window shows the data returned using the DMR++, the right shows the data read directly from the file using the server's builtin HDF4 reader.		To the right is a comparison of the same underlying data, the left window shows the data returned using the DMR++, the right shows the data read directly from the file using the server's builtin HDF4 reader.
	[[File:Data-comparison.png\|200px\|thumb\|right\|text-~~bottom~~\|Comparison of responses from a DMR++ and the native file handler.]]		[[File:Data-comparison.png\|200px\|thumb\|right\|text-top\|Comparison of responses from a DMR++ and the native file handler.]]

	====Simple shell command====		====Simple shell command====
Line 230:		Line 233:

	The DMR++ will appear when the command completes.		The DMR++ will appear when the command completes.

	~~ls -l~~

	~~shows~~

	(hyrax500) hyrax_git/HDF4-dir % ls -l		(hyrax500) hyrax_git/HDF4-dir % ls -l

Jimg: /* Building DMR++ files for HDF4 and HDF4-EOS2 (experimental) */

2024-08-29T00:13:39Z

Building DMR++ files for HDF4 and HDF4-EOS2 (experimental)

← Older revision		Revision as of 00:13, 29 August 2024
Line 94:		Line 94:
	Make a new directory in a convenient place and copy the HDF4 and/or HDF4-EOS2 files in that directory. Once you have the files in that directory, make an environment variable so it can be referred to easily. From inside the directory:		Make a new directory in a convenient place and copy the HDF4 and/or HDF4-EOS2 files in that directory. Once you have the files in that directory, make an environment variable so it can be referred to easily. From inside the directory:

	export HDF4_DIR=$(pwd)		export HDF4_DIR=$(pwd)

	Get the Docker container from Docker Hub using this command:		Get the Docker container from Docker Hub using this command:

	docker run -d -h hyrax -p 8080:8080 -v $HDF4_DIR:/usr/share/hyrax --name=hyrax opendap/hyrax:snapshot		docker run -d -h hyrax -p 8080:8080 -v $HDF4_DIR:/usr/share/hyrax --name=hyrax opendap/hyrax:snapshot

	What the options mean:		What the options mean:
Line 115:		Line 115:
	Check that the container is running using:		Check that the container is running using:

	docker ps		docker ps

	This will show a somewhat hard-to-read bit of information about all the running Docker container on you host:		This will show a somewhat hard-to-read bit of information about all the running Docker container on you host:

	CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS		CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS
	NAMES		NAMES
	2949d4101df4 opendap/hyrax:snapshot "/entrypoint.sh -" 15 seconds ago Up 14 seconds 8009/tcp, 8443/tcp,		2949d4101df4 opendap/hyrax:snapshot "/entrypoint.sh -" 15 seconds ago Up 14 seconds 8009/tcp, 8443/tcp,
	10022/tcp, 11002/tcp, 0.0.0.0:8080->8080/tcp hyrax		10022/tcp, 11002/tcp, 0.0.0.0:8080->8080/tcp hyrax

	If you want to stop containers, use		If you want to stop containers, use

	docker rm -f <CONTAINER ID>		docker rm -f <CONTAINER ID>

	where the ''CONTAINER ID'' for the one we just started and shown in the output of ''docker ps -a'' above is ''2949d4101df4''. No need to stop the container now, I'm just pointing out how to do it because it's often useful.		where the ''CONTAINER ID'' for the one we just started and shown in the output of ''docker ps -a'' above is ''2949d4101df4''. No need to stop the container now, I'm just pointing out how to do it because it's often useful.
Line 138:		Line 138:
	Get the command to return its help information:		Get the command to return its help information:

	docker exec -it hyrax get_dmrpp_h4 -h		docker exec -it hyrax get_dmrpp_h4 -h

	will return:		will return:

	<nowiki>usage: get_dmrpp_h4 [-h] -i I [-c CONF] [-s] [-u DATA_URL] [-D] [-v]		<nowiki>usage: get_dmrpp_h4 [-h] -i I [-c CONF] [-s] [-u DATA_URL] [-D] [-v]

	Build a dmrpp file for an HDF4 file. get_dmrpp_h4 -i h4_file_name. A dmrpp		Build a dmrpp file for an HDF4 file. get_dmrpp_h4 -i h4_file_name. A dmrpp
	file that uses the HDF4 file name will be generated.		file that uses the HDF4 file name will be generated.

	optional arguments:		optional arguments:

	...</nowiki>		...</nowiki>

	Lets build a DMR++ now, by explicitly using the container:		Lets build a DMR++ now, by explicitly using the container:

	docker exec -it hyrax bash		docker exec -it hyrax bash

	starts the ''bash'' shell in the container, with the current directory as root (/)		starts the ''bash'' shell in the container, with the current directory as root (/)

	[root@hyrax /]#		[root@hyrax /]#

	Change to the directory that is the root of the data (you'll see your HDF4 files in here):		Change to the directory that is the root of the data (you'll see your HDF4 files in here):

	cd /usr/share/hyrax		cd /usr/share/hyrax

	You will see, roughly:		You will see, roughly:

	<nowiki>[root@hyrax /]# cd /usr/share/hyrax		<nowiki>[root@hyrax /]# cd /usr/share/hyrax
	[root@hyrax hyrax]# ls		[root@hyrax hyrax]# ls
	3B42.19980101.00.7.HDF		3B42.19980101.00.7.HDF
	3B42.19980101.03.7.HDF		3B42.19980101.03.7.HDF
	3B42.19980101.06.7.HDF		3B42.19980101.06.7.HDF

	...</nowiki>		...</nowiki>

	In that directory, use the ''get_dmrpp_h4'' command to build a DMR++ document for one of the files:		In that directory, use the ''get_dmrpp_h4'' command to build a DMR++ document for one of the files:

	[root@hyrax hyrax]# get_dmrpp_h4 -i 3B42.20130111.09.7.HDF -u 'file:///usr/share/hyrax/3B42.20130111.09.7.HDF'		[root@hyrax hyrax]# get_dmrpp_h4 -i 3B42.20130111.09.7.HDF -u 'file:///usr/share/hyrax/3B42.20130111.09.7.HDF'

	Copy that pattern for whatever file you use. From the /usr/share/hyrax directory, you pass ''get_dmrpp_h4'' the name of the file (because it's local to the current directory) using the '''-i''' option. The '''-u''' option tells the command to embed the URL that follows it in the DMR++. I've used a ''file://'' URL to the file ''/usr/share/hyrax/3B42.19980101.00.7.HDF''.		Copy that pattern for whatever file you use. From the /usr/share/hyrax directory, you pass ''get_dmrpp_h4'' the name of the file (because it's local to the current directory) using the '''-i''' option. The '''-u''' option tells the command to embed the URL that follows it in the DMR++. I've used a ''file://'' URL to the file ''/usr/share/hyrax/3B42.19980101.00.7.HDF''.
Line 185:		Line 185:
	Lets look at how the ''hyrax'' service will treat that data file using the DMR++. In a browser, goto		Lets look at how the ''hyrax'' service will treat that data file using the DMR++. In a browser, goto

	http://localhost:8080/opendap/		http://localhost:8080/opendap/

	You will see [[File:Hyrax-including-new-DNRpp.png\|200px\|thumb\|right\|The running server shows the DMR++ as a dataset.]]		You will see [[File:Hyrax-including-new-DNRpp.png\|200px\|thumb\|right\|text-bottom\|The running server shows the DMR++ as a dataset.]]

	Click on the your equivalent of the '''3B42.20130111.09.7.HDF'' link, subset, download and open in Panoply or the equivalent. [[File:Hyrax-subsetting.png\|200px\|thumb\|right\|Use the form interface to subset and get a response.]]		Click on the your equivalent of the '''3B42.20130111.09.7.HDF'' link, subset, download and open in Panoply or the equivalent. [[File:Hyrax-subsetting.png\|200px\|thumb\|right\|text-bottom\|Use the form interface to subset and get a response.]]

	You can run batch tests in lots of files by building many DMR++ documents and then asking the server for various responses (nc4, dap) from the DMR++ and the original file. Those could be compared using various schemes, although in its entirety that is beyond this section's scope, the command ''getdap4'' is also included in the container and could be used to compare ''dap'' responses from the data file and the DMR++ document.		You can run batch tests in lots of files by building many DMR++ documents and then asking the server for various responses (nc4, dap) from the DMR++ and the original file. Those could be compared using various schemes, although in its entirety that is beyond this section's scope, the command ''getdap4'' is also included in the container and could be used to compare ''dap'' responses from the data file and the DMR++ document.

			Here is a comparison of the same underlying data, the left window shows the data returned using the DMR++, the right shows the data read directly from the file using the server's builtin HDF4 reader.
			[[File:Data-comparison.png\|200px\|thumb\|right\|text-bottom\|Comparison of responses from a DMR++ and the native file handler.]]

	====Simple shell command====		====Simple shell command====
Line 209:		Line 212:
	The command, written for the Bourne Shell, is:		The command, written for the Bourne Shell, is:

	<nowiki>#!/bin/bash		<nowiki>#!/bin/bash
	#		#
	# usage get_dmrpp_h4.sh <file>		# usage get_dmrpp_h4.sh <file>

	data_root=/usr/share/hyrax		data_root=/usr/share/hyrax

	cat <<EOF \| docker exec --interactive hyrax sh		cat <<EOF \| docker exec --interactive hyrax sh
	cd $data_root		cd $data_root
	get_dmrpp_h4 -i $1 -u "file://$data_root/$1"		get_dmrpp_h4 -i $1 -u "file://$data_root/$1"
	EOF</nowiki>		EOF</nowiki>

	Copy that, save it in a file (I named the file ''get_dmrpp_h4.sh'').		Copy that, save it in a file (I named the file ''get_dmrpp_h4.sh'').

Jimg: /* Building DMR++ files for HDF4 and HDF4-EOS2 (experimental) */

2024-08-28T23:59:59Z

Building DMR++ files for HDF4 and HDF4-EOS2 (experimental)

← Older revision		Revision as of 23:59, 28 August 2024
Line 142:		Line 142:
	will return:		will return:

	usage: get_dmrpp_h4 [-h] -i I [-c CONF] [-s] [-u DATA_URL] [-D] [-v]		<nowiki>usage: get_dmrpp_h4 [-h] -i I [-c CONF] [-s] [-u DATA_URL] [-D] [-v]

	Build a dmrpp file for an HDF4 file. get_dmrpp_h4 -i h4_file_name. A dmrpp		Build a dmrpp file for an HDF4 file. get_dmrpp_h4 -i h4_file_name. A dmrpp
Line 149:		Line 149:
	optional arguments:		optional arguments:

	...		...</nowiki>

	Lets build a DMR++ now, by explicitly using the container:		Lets build a DMR++ now, by explicitly using the container:
Line 165:		Line 165:
	You will see, roughly:		You will see, roughly:

	[root@hyrax /]# cd /usr/share/hyrax		<nowiki>[root@hyrax /]# cd /usr/share/hyrax
	[root@hyrax hyrax]# ls		[root@hyrax hyrax]# ls
	3B42.19980101.00.7.HDF		3B42.19980101.00.7.HDF
Line 171:		Line 171:
	3B42.19980101.06.7.HDF		3B42.19980101.06.7.HDF

	...		...</nowiki>

	In that directory, use the ''get_dmrpp_h4'' command to build a DMR++ document for one of the files:		In that directory, use the ''get_dmrpp_h4'' command to build a DMR++ document for one of the files:
Line 209:		Line 209:
	The command, written for the Bourne Shell, is:		The command, written for the Bourne Shell, is:

	#!/bin/bash		<nowiki>#!/bin/bash
	#		#
	# usage get_dmrpp_h4.sh <file>		# usage get_dmrpp_h4.sh <file>
Line 218:		Line 218:
	cd $data_root		cd $data_root
	get_dmrpp_h4 -i $1 -u "file://$data_root/$1"		get_dmrpp_h4 -i $1 -u "file://$data_root/$1"
	EOF		EOF</nowiki>

	Copy that, save it in a file (I named the file ''get_dmrpp_h4.sh'').		Copy that, save it in a file (I named the file ''get_dmrpp_h4.sh'').

Jimg: /* Building DMR++ files for HDF4 and HDF4-EOS2 (experimental) */

2024-08-28T23:43:19Z

Building DMR++ files for HDF4 and HDF4-EOS2 (experimental)

← Older revision		Revision as of 23:43, 28 August 2024
Line 115:		Line 115:
	Check that the container is running using:		Check that the container is running using:

	docker ps -a		docker ps

	This will show a somewhat hard-to-read bit of information about all the running Docker container on you host:		This will show a somewhat hard-to-read bit of information about all the running Docker container on you host:
Line 126:		Line 126:
	If you want to stop containers, use		If you want to stop containers, use

	docker rm -r <CONTAINER ID>		docker rm -f <CONTAINER ID>

	where the ''CONTAINER ID'' for the one we just started and shown in the output of ''docker ps -a'' above is ''2949d4101df4''. No need to stop the container now, I'm just pointing out how to do it because it's often useful.		where the ''CONTAINER ID'' for the one we just started and shown in the output of ''docker ps -a'' above is ''2949d4101df4''. No need to stop the container now, I'm just pointing out how to do it because it's often useful.
Line 132:		Line 132:
	====Lets run the DMR++ builder====		====Lets run the DMR++ builder====

	''At the end of this, I'll include a shell script that takes away many of these steps, but the script obscures some aspects of the command that you might want to tweak, so the following shows you all the details.''		''At the end of this, I'll include a shell script that takes away many of these steps, but the script obscures some aspects of the command that you might want to tweak, so the following shows you all the details. Skip to '''Simple shell command''' to skip over these details.''

	Make sure you are in the directory with the HDF4 files for these steps.		Make sure you are in the directory with the HDF4 files for these steps.
Line 175:		Line 175:
	In that directory, use the ''get_dmrpp_h4'' command to build a DMR++ document for one of the files:		In that directory, use the ''get_dmrpp_h4'' command to build a DMR++ document for one of the files:

	[root@hyrax hyrax]# get_dmrpp_h4 -i 3B42.~~19980101~~.00.7.HDF -u 'file:///usr/share/hyrax/3B42.~~19980101~~.00.7.HDF'		[root@hyrax hyrax]# get_dmrpp_h4 -i 3B42.20130111.09.7.HDF -u 'file:///usr/share/hyrax/3B42.20130111.09.7.HDF'

	Copy that pattern for whatever file you use. From the /usr/share/hyrax directory, you pass ''get_dmrpp_h4'' the name of the file (because it's local to the current directory). The '''-u''' option tells the command to embed the URL that follows it in the DMR++. I've used a ''file://'' URL to the file ''/usr/share/hyrax/3B42.19980101.00.7.HDF''.		Copy that pattern for whatever file you use. From the /usr/share/hyrax directory, you pass ''get_dmrpp_h4'' the name of the file (because it's local to the current directory) using the '''-i''' option. The '''-u''' option tells the command to embed the URL that follows it in the DMR++. I've used a ''file://'' URL to the file ''/usr/share/hyrax/3B42.19980101.00.7.HDF''.

	Note the three slashes following the colon. Obscure, but it makes sense.		Note the three slashes following the colon, two from the way a URL names a protocol and one because the pathname starts at the root directory. Obscure, but it makes sense.

	~~Build ing~~ the DMR++ and embedding a ''file://'' URL will enable testing the DMR+~~+ easily~~.		Building the DMR++ and embedding a ''file://'' URL will enable testing the DMR+.

	Lets look at how the ''hyrax'' service will treat that data file using the DMR++. In a browser, goto		Lets look at how the ''hyrax'' service will treat that data file using the DMR++. In a browser, goto
Line 187:		Line 187:
	http://localhost:8080/opendap/		http://localhost:8080/opendap/

	You will see [[File:Hyrax-including-new-DNRpp.png\|200px\|thumb\|right\|~~Caption~~]]		You will see [[File:Hyrax-including-new-DNRpp.png\|200px\|thumb\|right\|The running server shows the DMR++ as a dataset.]]

	Click on the your equivalent of the '''3B42.~~19980101~~.00.7.HDF~~.dmrpp~~'' link, subset, download and open in Panoply or the equivalent. [[File:Hyrax-subsetting.png\|200px\|thumb\|right\|~~Caption~~]]		Click on the your equivalent of the '''3B42.20130111.09.7.HDF'' link, subset, download and open in Panoply or the equivalent. [[File:Hyrax-subsetting.png\|200px\|thumb\|right\|Use the form interface to subset and get a response.]]

			You can run batch tests in lots of files by building many DMR++ documents and then asking the server for various responses (nc4, dap) from the DMR++ and the original file. Those could be compared using various schemes, although in its entirety that is beyond this section's scope, the command ''getdap4'' is also included in the container and could be used to compare ''dap'' responses from the data file and the DMR++ document.

			====Simple shell command====

			Here is a simple shell command that you can run on the host computer that will eliminate most of the above.

			''In the spirit of a recipe, I'll restate the earlier command for starting the docker container with the '''get_dmrpp_h4''' command and the '''hyrax''' server.''

			Start the container:

			docker run -d -h hyrax -p 8080:8080 -v $HDF4_DIR:/usr/share/hyrax --name=hyrax opendap/hyrax:snapshot

			Is it running:

			docker ps

	=~~==Command line option===~~		The command, written for the Bourne Shell, is:

			#!/bin/bash
			#
			# usage get_dmrpp_h4.sh <file>

			data_root=/usr/share/hyrax

			cat <<EOF \| docker exec --interactive hyrax sh
			cd $data_root
			get_dmrpp_h4 -i $1 -u "file://$data_root/$1"
			EOF

			Copy that, save it in a file (I named the file ''get_dmrpp_h4.sh'').

			Run the command on the host (not the docker container) and in the directory with the HDF4 files (you don't ''have'' to do that, but sorting out the details is left as an exercise for the reader ;-). Run the command like this:

			./get_dmrpp_h4.sh AMSR_E_L3_SeaIce25km_V15_20020601.hdf

			The DMR++ will appear when the command completes.

			ls -l

			shows

			(hyrax500) hyrax_git/HDF4-dir % ls -l
			total 1251240
			-rw-r--r--@ 1 jimg staff 1250778 Aug 22 22:31 AMSR_E_L2_Land_V09_200206191112_A.hdf
			-rw-r--r--@ 1 jimg staff 20746207 Aug 22 22:32 AMSR_E_L3_SeaIce25km_V15_20020601.hdf
			-rw-r--r-- 1 jimg staff 3378674 Aug 28 17:37 AMSR_E_L3_SeaIce25km_V15_20020601.hdf.dmrpp

	==Building ''dmr++'' files with get_dmrpp==		==Building ''dmr++'' files with get_dmrpp==