Timing and X-ray Spectral Features of Swift J1626.6-5156

In this paper, we extend timing analysis of Baykal et al. (2010) of \src using RXTE-PCA observations between MJD 53724 and MJD 55113 together with a Chandra-ACIS observation on MJD 54897 with a 20 ks exposure. We also present X-ray spectral analysis of these RXTE and Chandra observations. We find that the spin-up rate of the source is correlated with the X-ray flux. Using this correlation, we estimate the distance and surface magnetic field of the source as $\sim 15$kpc and $\sim 9\times 10^{11}$Gauss respectively. From the spectral analysis, we found that power law index increases and Hydrogen column density decreases with decreasing flux.Comment: Revised version; 12 pages, 4 figures, accepted for publication in MNRA

Pulse Profiles of Swift J1626.6+5156

In this paper, we analyzed pulse profiles of Swift J1626.6+5156 using the lightcurves from RXTE-PCA observations between MJD 53724 (just after the outburst) and MJD 55113 and a Chandra-ACIS dataset on MJD 54897 with a 20 ks exposure. We found that pulse profiles show morphological variations and pulsations do not cease even $\sim 1200$ days after the outburst. Despite these variations, we did not find any significant variation in the pulsed fraction with decreasing X-ray flux.Comment: 4 pages, 2 figures, Conference proceeding of "Astrophysics of Neutron Stars 2010 -- a conference in honor of M. Ali Alpar", 2-6 August 2010, Cesme, Izmir, Turke

A Workflow System through Cooperating Agents for Control and Document Flow over the Internet

In this paper we describe an architecture that provides for automating and monitoring the flow of control and document over the Internet among different organizations, thereby creating a platform necessary to describe higher order processes involving several organizations and companies. The higher order process is designed through a graphical user interface and mapped to the textual workflow definition language of the system called FlowDL. A process definition in FlowDL is executed through cooperating agents that are automatically initialized at each site that the process executes. Agents handle the activities at their site, provide for coordination with other agents in the system by routing the documents in electronic form according to the process description. The system is capable of activating external applications (which may be inside the company firewall) when necessary, keeping track of process information, and providing for the security and authentication of documents as well ..

The MARIFlow Workflow Management System

MARIFlow System [1] provides for automating and monitoring the flow of control and data over the Internet among different organizations, thereby creating a platform necessary to describe higher order processes involving several organizations and companies. The architecture is general enough to be applied to any business practice where data flow among different industries and cooperations and the invocation of activities follow a pattern that can be described through a process definition. The example application provided within the scope of this project is on maritime industry A MARIFlow process is executed through cooperating agents, called MARCAs (MARIFlow Cooperating Agents) that are automatically initialized at each site that the process executes. MARCAs handle the activities at their site, provide for coordination with other MARCAs in the system by routing the documents in electronic form according to the process description, keeping track of process information, and providing for the security and authentication of documents as well as comprehensive monitoring facilities. More specifically, the functionality provided by the system is as follows: ¯ A declarative means to specify the control of document flow over the Internet where it is possible to define the source of data, its control flow and the activities that make use of this data. ¯ A fully distributed execution architecture achieved through cooperating agents over the Internet. The agents know about other agents that they need to communicate with and preserve their state during communication. They also manage local information for monitoring purposes and for recovering from failures. ¯ Communicating with inside firewall applications. A MARCA can activate in-house activities automati