Kepler: Issueshttps://projects.ecoinformatics.org/ecoinfo/https://projects.ecoinformatics.org/ecoinfo/ecoinfo/favicon.ico?14691340362012-05-07T23:52:44ZEcoinformatics Redmine
Redmine Bug #5602 (Resolved): Timezone confusion using the schedulerhttps://projects.ecoinformatics.org/ecoinfo/issues/56022012-05-07T23:52:44ZDerik Barseghianbarseghian@nceas.ucsb.edu
<p>It appears at least some parts of the Workflow Scheduling system don't account for different timezones. When you schedule a workflow in Kepler, you don't specify timezone, so presumably this is local time. I think the server also uses local time, and so this requires you to know where the server resides, and schedule using its time. Instead we should probably translate to GMT, and expose timezone codes in the gui.</p> Bug #5319 (Resolved): The workflow which archive sensor data into metacat can upload incorrect da...https://projects.ecoinformatics.org/ecoinfo/issues/53192011-02-23T00:20:48ZJing Taotao@nceas.ucsb.edu
<p>I used sensor simulator to create data set, then killed the simulator. It created data with timestamp from 2011-02-22 03:16:54 to 2011-02-22 03:17:52.</p>
<p>I ran the workflow and got the eml has the title:<br />Dataset for sensor:"sensor0" at site:"gpp" for time period "2011-02-22 03:16:54" and "2011-02-22 03:17:52"</p>
<p>I checked the data file in metacat and it has the data<br />from 2011-02-22 03:16:54 to 2011-02-22 03:17:52</p>
<p>Everything looks good.</p>
<p>Then I ran the sensor simulator again and created some new data. Then I killed the simulator. It created data with timestamp from 2011-02-22 03:57:35 to 2011-02-22 03:58:33</p>
<p>I ran the workflow again and two eml documents were uploaded:<br />1. Dataset for sensor:"sensor0" at site:"gpp" for time period "2011-02-22 03:16:54" and "2011-02-22 03:58:33"</p>
<p>2. Dataset for sensor:"sensor0" at site:"gpp" for time period "2011-02-22 03:57:35" and "2011-02-22 03:58:33"</p>
<p>I double checked the data file in metacat and found the data files comply with the metadata.</p>
<p>From the title, we can see the dataset 1 combines both dataset 2 and the previous dataset which was uploaded in the last time.</p>
<p>So we have the duplicated data. The second run should only create the dataset 2.</p> Bug #5303 (Resolved): The workflow which archive sensor data into metacat can upload data even no...https://projects.ecoinformatics.org/ecoinfo/issues/53032011-02-12T01:12:25ZJing Taotao@nceas.ucsb.edu
<p>I used sensor stimulator and span to generate some data into a Dataturbine server.<br />Then i terminated the sensor stimulator and span. So no new data will be generate anymore.</p>
<p>Supposely the workflow can upload data only at the first time. The second run will be no data uploaded.</p>
<p>However, I can keep running the workflow and every time data and metadata are uploaded to the metacat server</p> Bug #5274 (Resolved): Trying to schedule workflow with report layout puts up prompt about no repo...https://projects.ecoinformatics.org/ecoinfo/issues/52742011-01-14T00:07:27ZDerik Barseghianbarseghian@nceas.ucsb.edu
<p>To reproduce:<br />create a workflow<br />create a report design<br />File-> Save to kar<br />Tools->Workflow Scheduler<br />Find and select this workflow. You'll be prompted to upload. Say yes, and then you'll get a warning telling you this kar doesn't have a report layout, so no run kar will be created.</p> Bug #5251 (Resolved): using File->Open MoML... always opens model into Sensor Site viewhttps://projects.ecoinformatics.org/ecoinfo/issues/52512010-12-02T19:28:18ZDerik Barseghianbarseghian@nceas.ucsb.edu
<p>If in the sensor-view suite I open a regular xml model, e.g. 00-StatisticalSummary.xml, using the File->Open MoML... menu item, the new window is in the the Sensor Site view, with filtered component tree. <br />It should just open into the Workflow view. This is on mac and linux at r26412.</p> Bug #5236 (Resolved): The list on the left panel of the scheduler should only show WF objects tha...https://projects.ecoinformatics.org/ecoinfo/issues/52362010-11-02T19:01:14ZJing Taotao@nceas.ucsb.edu
<p>In the scheduler, the list on the left should only show WF objects that<br />can be scheduled.</p> Bug #5226 (Resolved): User should be warned to design a report if there isn't a report when sched...https://projects.ecoinformatics.org/ecoinfo/issues/52262010-10-28T01:53:42ZJing Taotao@nceas.ucsb.edu
<p>The user should be warned to design a report and upload it if there isn't a report when scheduling. Matt think this part of the system is not obvious.</p> Bug #5223 (Resolved): Store the last timestamp of data store for a sensor to the local databasehttps://projects.ecoinformatics.org/ecoinfo/issues/52232010-10-20T21:33:34Zmanish manishmkanand@gmail.com
<p>Once the data set for a specific time interval is stored in the metacat, we need to store the last timestamp interval, so that we know since when to start retrieving the next datasets for the same sensor, when we make a read connection to the dataturbine server. This feature is achieved by storing this information in the local mysql db. This same information will be read when the next chunking needs to be done for the dataset.</p> Bug #5222 (Resolved): Store data set file and associated EML file into metacathttps://projects.ecoinformatics.org/ecoinfo/issues/52222010-10-20T21:30:28Zmanish manishmkanand@gmail.com
<p>Given a data set file path and the EML file, store the data and EML file to metacat. Seems that we use the already existing EcoGridWriter to achieve this functionality.</p> Bug #5201 (Resolved): track changes on span serverhttps://projects.ecoinformatics.org/ecoinfo/issues/52012010-10-15T21:55:29ZDaniel Crawldanielcrawl@gmail.com
<p>When a command is successfully issued to a SPAN server, e.g., turn sensor off, change sampling rate, etc., the command should be logged to the DataTurbine server. This is required so that accurate EML and SensorML documents can be constructed to describe the sensor site.</p> Bug #5033 (Resolved): Workflow Run Manager - Allow multiple instances of WRM in one Kepler instancehttps://projects.ecoinformatics.org/ecoinfo/issues/50332010-05-27T19:50:09ZDerik Barseghianbarseghian@nceas.ucsb.edu
<p>As Figure 6 implies, each Kepler window has a WRM that may be showing run results on a different server:<br /><a class="external" href="https://kepler-project.org/developers/incubation/kepler-engineering-view-for-reap/engineering-view-plans">https://kepler-project.org/developers/incubation/kepler-engineering-view-for-reap/engineering-view-plans</a></p> Bug #5032 (Resolved): Workflow Run Manager - ability to connect to different prov stores from gui...https://projects.ecoinformatics.org/ecoinfo/issues/50322010-05-27T19:46:57ZDerik Barseghianbarseghian@nceas.ucsb.edu
<p>WRM must be able to dynamically connect to and show runs in remote provenance stores based on what a user has clicked on.</p>
<p>See Figure 6: <a class="external" href="https://kepler-project.org/developers/incubation/kepler-engineering-view-for-reap/engineering-view-plans">https://kepler-project.org/developers/incubation/kepler-engineering-view-for-reap/engineering-view-plans</a></p> Bug #4757 (Resolved): transfer sensor data from dataturbine to metacathttps://projects.ecoinformatics.org/ecoinfo/issues/47572010-02-05T18:48:31ZDaniel Crawldanielcrawl@gmail.com
<p>Periodically archive sensor data on the dataturbine server into metacat. Also verify that archived sensor data can be searched and read in Kepler.</p> Bug #4755 (Resolved): update workflow run manager and reporting to display runs of sensor workflowshttps://projects.ecoinformatics.org/ecoinfo/issues/47552010-02-05T18:44:50ZDaniel Crawldanielcrawl@gmail.com
<p>Show the current and past runs of sensor workflows executed on the server in the workflow run manager. Additionally, make it easy to show generated reports of past runs, e.g., clicking on a wrm row will show the report.</p>
<p>See figure 6 in <a class="external" href="https://kepler-project.org/developers/incubation/kepler-engineering-view-for-reap/engineering-view-plans">https://kepler-project.org/developers/incubation/kepler-engineering-view-for-reap/engineering-view-plans</a></p> Bug #4754 (Resolved): update metacat workflow execution schedulerhttps://projects.ecoinformatics.org/ecoinfo/issues/47542010-02-05T18:40:53ZDaniel Crawldanielcrawl@gmail.com
<p>Make any changes necessary to the workflow execution scheduler in Metacat to provide the functionality for bug 4753. Possibly move the code out of Metacat and into the engineering view module or a new Kepler module.</p>