Hi all,
sure, as Co-Mentor I would like to join the meeting.
Best regards,
Martin
--------------------------------------------------
Dipl.-Ing. Martin Melik-Merkumians
Advanced Mechatronic Systems
Automation and Control Institute (ACIN)
TU Wien
DVR-Number: 0005886
Gusshausstr.
27-29, room CA-05-38
1040 Vienna, Austria
Phone: +43 (0)1 588 01 37688
Fax: +43 (0)1 588 01 937688
Email:
melik-merkumians@xxxxxxxxxxxxxxxxx
http://www.acin.tuwien.ac.at/
--------------------------------------------------
Von: 4diac-dev-bounces@xxxxxxxxxxx <4diac-dev-bounces@xxxxxxxxxxx>
Im Auftrag von Alois Zoitl
Gesendet: Montag, 4. Mai 2020 22:21
An: 4diac developer discussions <4diac-dev@xxxxxxxxxxx>
Betreff: Re: [4diac-dev] GSOC - OCL Topic
it is a great pleasure for me to announce that Sándor's Google Summer of Code Project was officially accepted by Google. I'm looking forward to work with you on the OCL topic. For getting started I think it would be best to have a short
web-meeting so that we get to know each other. Maybe other committers want to join as well.
Do you have a short overview of your planned project we could use for our news section?
On Tue, 2020-03-31 at 09:47 +0200, Sándor Bácsi wrote:
Hi,
I uploaded the final proposal. Thank you very much for the review.
Xtext: I definitely want to get familiar with the Xtext projects of the 4diac IDE, but I haven't had the time yet.
IEC 61499: I would really appreciate additional materials. I am thinking of buying the book "Modelling Control Systems Using IEC 61499 2nd edition".
Regards,
Sándor
Hi Sandor,
thanks for pre-sharing the proposal. I must say for me it is a very good one. There is not really anything I can add. What I find quite interesting is that you
also mention XText. Because here we definitely want to improve.
One thing that would be interesting for the development stage is how to represent the output of the OCL. I had in mind something like the errors and warning
view. But maybe there are better options.
Regarding your concerns about learning IEC 61499. This is definitely something where we, the 4diac committers, can be supporting. Many of us regularly teach IEC
61499. So we even have additional material and can also help in discussing different aspects of the IEC 61499 modeling language.
But this would then be something for the community bonding period. For now I can only keep my fingers crossed.
Cheers,
Alois
On Mon, 2020-03-30 at 11:50 +0200, Sándor Bácsi wrote:
> Hi,
>
> I would really appreciate any feedback on my proposal:
>
https://docs.google.com/document/d/1cuvEnxFl8AHnaquYVec44UcuiEfxWqesdB4IDkeS1Vg/edit?usp=sharing
>
> Thank you!
>
> Sandor
>
> Alois Zoitl <alois.zoitl@xxxxxx> ezt írta (időpont: 2020. márc. 27., P, 21:40):
> > Hi Sándor,
> >
> > welcome to Eclipse 4diac. I'm very happy that you are interested in the OCL GSoC topic. This is a topic that we wished to have already for a longer time.
> >
> > Your firs prototype seems to be quite interesting. I think that checking types (e.g., basic function blocks) has some even lower hanger fruits. BTW any feedback to improve our ECore models is also very appreciated.
> >
> > Regarding your proposal question: we don't have a specific Eclipse 4diac template. The generic structure would be fine for us. You can also submit a first proposal as draft and give us a link here if you want first feedback from us.
> >
> > Cheers,
> > Alois
> >
> >
> > On Fri, 2020-03-27 at 11:07 +0100, Sándor Bácsi wrote:
> > > Hi,
> > >
> > > I am a 1st year PhD student at the University of Technology, Hungary. I got interested in the OCL project, since it is related to my research. I spent the last few weeks getting to know the 4diac IDE and the IEC 61499 standard. I implemented a simple
feature that allows checking the validation results for an Application. I converted the lib.ecore model to an OCLinEcore document, which makes more convenient to specify OCL constraints in the OCLinEcore Editor. The validation results can be displayed choosing
"Validate" from the context menu of an application.
> > >
> > >
> > >
> > > So far, I only created simple OCL constraints, like an OCL invariant for checking the value for certain VarDeclarations. For example, a DTMustHaveValue invariant tested on the BlinkApp tutorial:
> > >
> > >
> > >
> > >
> > > I know these results are rudimentary, but I wanted to share this little progress. I realized that I need to gain more experience in the IEC 61499 standard so that I can find out more advanced constraints which are capable of identifying inconsistencies
in the models.
> > >
> > > I would like to submit a proposal to the 4diac OCL topic, but I am a bit confused regarding the proposal. Is there a conventional 4diac specific template for the proposal? On the official GSOC page (https://summerofcode.withgoogle.com/organizations/4590106242973696/),
there is a guidance for submitting a proposal (Abstract, Detailed Information, Experience, Background, etc.). Is it okay to follow this format?
> > >
> > > Regards,
> > >
> > > Sándor
> > > _______________________________________________
> > > 4diac-dev mailing list
> > > 4diac-dev@xxxxxxxxxxx
> > >
> > > To unsubscribe from this list, visit
> > >
https://www.eclipse.org/mailman/listinfo/4diac-dev
> > >
> >
> > _______________________________________________
> > 4diac-dev mailing list
> > 4diac-dev@xxxxxxxxxxx
> > To unsubscribe from this list, visit
https://www.eclipse.org/mailman/listinfo/4diac-dev
_______________________________________________
4diac-dev mailing list
4diac-dev@xxxxxxxxxxx
To unsubscribe from this list, visit
https://www.eclipse.org/mailman/listinfo/4diac-dev
|
