Analisis kelayakan usaha perikanan pukat pantai di kecamatan Pusomaen kabupaten Minahasa Tenggara

Potensi sumberdaya perikanan laut Indonesia diperkirakan sebesar 6,40 juta ton per tahun, di mana 4,78 juta ton (73,43%) adalah sumberdaya ikan pelagis. Provinsi Sulawesi Utara memiliki sumberdaya perikanan yang cukup potensial untuk dikelola karena masih di bawah potensial lestari yang ditetapkan oleh pemerintah. Usaha penangkapan ikan merupakan suatu kegiatan nelayan untuk menghidupi/memenuhi perekonomian yang memanfaatkan sumberdaya hayati perairan dengan tujuan mendapatkan keuntungan. Di Kecamatan Pusomaen Kabupaten Minahasa Tenggara ada satu alat tangkap soma dampar atau pukat pantai (Beach Seine). Hal ini dikarenakan usaha alat tangkap soma dampar masih sangat menjanjikan.Tujuan dari penelitian ini adalah untuk menganalisis kelayakan usaha perikanan pukat pantai dalam bidang teknologi penangkapan ikan di Kecamatan Pusomaen Kabupaten Minahasa Tenggara. Penelitian ini menggunakan metode survei dengan melakukan wawancara. Berdasarkan hasil penelitian terdapat empat indikator yang dijadikan fokus penelitian ini,yaitu: 1.Pendapatan usaha,2. RevenueCost Ratio (R/C Ratio),3. Payback periode (PP),4. Return of investment (ROI). Berdasarkan observasi yang dilakukan di Kecamatan Posumaen di Kabupaten Minahasa Tenggara terkait kelayakan usaha perikanan pukat pantai sudah cukup baik, akan tetapi masih terdapat beberapa kendala yang ditemui pada pengumpulan data/survei tersebut. Masyarakat nelayan di Kecamatan Pusomaen masih tetap menggunakan pukat pantai (Beach Seine) karena modal yang dikeluarkan dalam mengoperasikan alat tangkap pukat pantai cukup murah, hanya dengan menggunakan tenaga saja

Is Entrepreneurial Success Predictable? An Ex-Ante Analysis of the Character-Based Approach

This paper empirically analyzes whether the character-based approach, which focuses on the personality structure and the human capital of business founders, allows prediction of entrepreneurial success. A unique data set is used consisting of 414 persons whose personal characteristics were analyzed by different methods, namely an one-day assessment center (AC) and a standardized questionnaire, before they launched their business. Results are partly unexpected and weaker than previous ex-post findings: first, we found correlations between the AC data and the questionnaire in one subgroup only. Second, the predictive power of the AC data is slightly better than that of the questionnaire, but lower than expected in theory. Interestingly, for those subgroups where the AC data have low predictive power, the questionnaire does better. Third, when success is measured in terms of employees hired, the character-based approach is a poor predictor. Copyright 2008 The Authors.

Channels as Objects in Concurrent Object-Oriented Programming

There is often a sort of a protocol associated to each class, stating when and how certain methods should be called. Given that this protocol is, if at all, described in the documentation accompanying the class, current mainstream object-oriented languages cannot provide for the verification of client code adherence against the sought class behaviour. We have defined a class-based concurrent object-oriented language that formalises such protocols in the form of usage types. Usage types are attached to class definitions, allowing for the specification of (1) the available methods, (2) the tests clients must perform on the result of methods, and (3) the object status - linear or shared - all of which depend on the object's state. Our work extends the recent approach on modular session types by eliminating channel operations, and defining the method call as the single communication primitive in both sequential and concurrent settings. In contrast to previous works, we define a single category for objects, instead of distinct categories for linear and for shared objects, and let linear objects evolve into shared ones. We introduce a standard sync qualifier to prevent thread interference in certain operations on shared objects. We formalise the language syntax, the operational semantics, and a type system that enforces by static typing that methods are called only when available, and by a single client if so specified in the usage type. We illustrate the language via a complete example.Comment: In Proceedings PLACES 2010, arXiv:1110.385

Poly(ADP-Ribose) Polymerase 1 (PARP-1) Regulates Ribosomal Biogenesis in Drosophila Nucleoli

Poly(ADP-ribose) polymerase 1 (PARP1), a nuclear protein, utilizes NAD to synthesize poly(AD-Pribose) (pADPr), resulting in both automodification and the modification of acceptor proteins. Substantial amounts of PARP1 and pADPr (up to 50%) are localized to the nucleolus, a subnuclear organelle known as a region for ribosome biogenesis and maturation. At present, the functional significance of PARP1 protein inside the nucleolus remains unclear. Using PARP1 mutants, we investigated the function of PARP1, pADPr, and PARP1-interacting proteins in the maintenance of nucleolus structure and functions. Our analysis shows that disruption of PARP1 enzymatic activity caused nucleolar disintegration and aberrant localization of nucleolar-specific proteins. Additionally, PARP1 mutants have increased accumulation of rRNA intermediates and a decrease in ribosome levels. Together, our data suggests that PARP1 enzymatic activity is required for targeting nucleolar proteins to the proximity of precursor rRNA; hence, PARP1 controls precursor rRNA processing, post-transcriptional modification, and pre-ribosome assembly. Based on these findings, we propose a model that explains how PARP1 activity impacts nucleolar functions and, consequently, ribosomal biogenesis

Typechecking Java Protocols with [St]Mungo

This is a tutorial paper on [St]Mungo, a toolchain based on multiparty session types and their connection to typestates for safe distributed programming in Java language. The StMungo (“Scribble-to-Mungo”) tool is a bridge between multiparty session types and typestates. StMungo translates a communication protocol, namely a sequence of sends and receives of messages, given as a multiparty session type in the Scribble language, into a typestate specification and a Java API skeleton. The generated API skeleton is then further extended with the necessary logic, and finally typechecked by Mungo. The Mungo tool extends Java with (optional) typestate specifications. A typestate is a state machine specifying a Java object protocol, namely the permitted sequence of method calls of that object. Mungo statically typechecks that method calls follow the object’s protocol, as defined by its typestate specification. Finally, if no errors are reported, the code is compiled with javac and run as standard Java code. In this tutorial paper we give an overview of the stages of the [St]Mungo toolchain, starting from Scribble communication protocols, translating to Java classes with typestates, and finally to typechecking method calls with Mungo. We illustrate the [St]Mungo toolchain via a real-world case study, the HTTP client-server request-response protocol over TCP. During the tutorial session, we will apply [St]Mungo to a range of examples having increasing complexity, with HTTP being one of them

Capabilities for Uniqueness and Borrowing

An important application of unique object references is safe and efficient message passing in concurrent object-oriented programming. However, to prevent the ill effects of aliasing, practical systems often severely restrict the shape of messages passed by reference. Moreover, the problematic interplay between destructive reads--often used to implement unique references--and temporary aliasing through "borrowed" references is exacerbated in a concurrent setting, increasing the potential for unpredictable run-time errors. This paper introduces a new approach to uniqueness. The idea is to use capabilities for enforcing both at-most-once consumption of unique references, and a flexible notion of uniqueness. The main novelty of our approach is a model of uniqueness and borrowing based on simple, unstructured capabilities. The advantages are: first, it provides simple foundations for uniqueness and borrowing. Second, it can be formalized using a relatively simple type system, for which we provide a complete soundness proof. Third, it avoids common problems involving borrowing and destructive reads, since unique references subsume borrowed references. We have implemented our type system as an extension to Scala. Practical experience suggests that our system allows type checking real-world actor-based concurrent programs with only a small number of additional type annotations