![]() ![]() If is not entered then STK will create a unique name for the duplicate template.Īdd a user description to the specified Time component or template. ![]() If is not entered then STK will create a unique name for the duplicate component.ĭuplicate the specified Time template using the, if entered. Rename the specified Time template to the new name.ĭuplicate the specified Time component using the, if entered. Rename the specified Time component to the new name. specifies the parent of the imported components. Import the components from the specified "". This parameter can be entered multiple times on the command line.Īll components exported to one file must have the same parent. "" is the name of a component to be exported. See Specifying Paths for "" syntax information. "" can be the path to a file on your local drive or the path to a file on an SDF server. If the file already exists it will be overwritten. "" is the file that will be written, it should have the extension. The Clear option is not valid for a template.Įxport the specified components to a file. The Compute option is not valid for a template.Ĭlear the Time component.This command will Nack if the component is already cleared or cannot be cleared. To get the Compute/Clear status of a Time component use the TimeTool_R command with the Status option. ![]() This command will Nack if the component is already computed or cannot be computed. The TimeTool command is not valid for CommSystem, Constellation, Planet, or Star objects, or Central Bodies. These user-created structures and elements can then be used in STK for reporting and graphing as well as 2D and 3D graphic displays. The TimeTool command enables you to define instances, intervals of time, time arrays and collections of intervals. Returns: None or instance of 2 with Analyze results.Description | Example | Return message | Group TimeToolĭefine components defining instances or intervals of time. TASCO TIMETOOL WILL NOT EXECUTE UPDATEIt is important to call this on reference shots to update TimeTool’s Invokes TimeTool.Analyze to process a event. isRefShot ( ) ¶ isRefShot(self, evt): returns True if this is a reference shot - meaning laser is on, but beam is off. endJob ( ) ¶ beginCalibCycle(self, evt, env): called by psana framework if/after all datasource events have been processed endRun ( ) ¶ beginCalibCycle(self, evt, env): called by psana framework when an end run is found duringĮvent iteration. Initialize the the AnalyzeOptions object with the parameter controlLogic=True endCalibCycle ( ) ¶ endCalibCycle(self, evt, env): called by psana framework when an end calibcycle is found duringĮvent iteration. controlLogic ( ) ¶ controlLogic(self, laserOn, beamOn): this is for unusal cases when one wants to directly define beginJob ( ) ¶ beginJob(self, evt, env): called by psana framework when datasource is created beginRun ( ) ¶ beginRun(self, evt, env): called by psana framework for each new run duringĮvent iteration. Set controlLogic=True in AnalyzeOptions and use the controlLogic(beamOn, laserOn) function beginCalibCycle ( ) ¶ beginCalibCycle(self, evt, env): called by psana framework for each new calibcycle duringĮvent iteration. Underlying C++ TimeTool.Analyze module twice. The PyAnalyze class caches the results of the first call so as to not call the Note that it is Ok to call the PyAnalyze.process(evt) function more than once on the For idx, evt in enumerate(ds.events()): if ttAnalyze.isRefShot(evt): ttAnalyze.process(evt) if idx % numberOfRanks != rank: continue ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |